[PATCH] pipeline: support conversion between big and small fields
Thomas Monjalon
thomas at monjalon.net
Sun Feb 19 23:18:12 CET 2023
10/02/2023 20:51, Cristian Dumitrescu:
> While the small fields (size <= 64 bits) can be in either network byte
> order (header fields) or host byte order (meta-data fields), the big
> fields (size > 64 bits) are always expected to be in network byte
> order (big endian), both header and metadata fields.
>
> Previously, a big field could be involved in an assignment only when
> both the destination and the source are big fields of exactly the same
> size. This restriction is now relaxed significantly: in case a big
> field is involved as either destination or source, the other field can
> now be either a big field (of the same or different size) or a small
> header field, so in either case both destination and source are in the
> network byte order.
>
> Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu at intel.com>
> Signed-off-by: Kamalakannan R <kamalakannan.r at intel.com>
Applied, thanks.
More information about the dev
mailing list