All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] pipeline: fix endianness conversions
Date: Tue, 20 Apr 2021 02:34:43 +0200	[thread overview]
Message-ID: <3640647.UQ6DxFeTdr@thomas> (raw)
In-Reply-To: <20210403001709.75890-1-cristian.dumitrescu@intel.com>

03/04/2021 02:17, Cristian Dumitrescu:
> The SWX pipeline instructions work with operands of different types:
> header fields (h.header.field), packet meta-data (m.field), extern
> object mailbox field (e.obj.field), extern function (f.field), action
> data read from table entries (t.field), or immediate values; hence the
> HMEFTI acronym. The H operands are stored in network byte order (NBO),
> while the MEFT operands are stored in host byte order (HBO), hence the
> need to operate endianness conversions.
> 
> Some of the endianness conversion macros were not working correctly
> for some cases such as operands of different sizes, and they are fixed
> now. Affected instructions: mov, and, or, xor, jmpeq, jmpneq.
> 
> Fixes: 7210349d5baa ("pipeline: add SWX move instruction")
> Fixes: 650195cf965a ("pipeline: introduce SWX and instruction")
> Fixes: 8f796198dcda ("pipeline: introduce SWX or instruction")
> Fixes: b4e607f9fd5e ("pipeline: introduce SWX XOR instruction")
> Fixes: b3947e25bed4 ("pipeline: introduce SWX jump and return instructions")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>

Applied, thanks




      reply	other threads:[~2021-04-20  0:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03  0:17 [dpdk-dev] [PATCH] pipeline: fix endianness conversions Cristian Dumitrescu
2021-04-20  0:34 ` Thomas Monjalon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3640647.UQ6DxFeTdr@thomas \
    --to=thomas@monjalon.net \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.