patches for DPDK stable branches
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Radu Nicolau <radu.nicolau@intel.com>
Cc: Jingjing Wu <jingjing.wu@intel.com>,
	Beilei Xing <beilei.xing@intel.com>,
	dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/iavf: fix IAVF_TX_OFFLOAD_MASK definition
Date: Tue, 24 Oct 2023 11:49:39 +0200	[thread overview]
Message-ID: <CAJFAV8wOdie9ruPd=W4jC7HXRuvbMCrUZwUvusHZD=TCqch79A@mail.gmail.com> (raw)
In-Reply-To: <20231024091328.11933-1-radu.nicolau@intel.com>

On Tue, Oct 24, 2023 at 11:13 AM Radu Nicolau <radu.nicolau@intel.com> wrote:
>
> IAVF_TX_OFFLOAD_MASK definition contained
> RTE_ETH_TX_OFFLOAD_SECURITY instead of
> RTE_MBUF_F_TX_SEC_OFFLOAD.
>
> Fixes: 6bc987ecb860 ("net/iavf: support IPsec inline crypto")
> Cc: stable@dpdk.org
>
> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>

Something is not clear to me.
How was the IPsec inline crypto feature supposed to work with this
driver so far?

Any packet with the RTE_MBUF_F_TX_SEC_OFFLOAD flag should have been
refused in iavf_prep_pkts.


-- 
David Marchand


  reply	other threads:[~2023-10-24  9:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24  9:13 Radu Nicolau
2023-10-24  9:49 ` David Marchand [this message]
2023-10-24 10:22   ` Radu Nicolau
2023-10-24 11:24     ` Zhang, Qi Z
2023-10-24 14:48       ` Radu Nicolau
2023-10-24 23:30         ` Zhang, Qi Z
2023-10-25  9:01           ` Radu Nicolau
2023-10-25  9:07             ` David Marchand
2023-10-25 10:14               ` Radu Nicolau
2023-10-25  1:50 ` Zhang, Qi Z

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='CAJFAV8wOdie9ruPd=W4jC7HXRuvbMCrUZwUvusHZD=TCqch79A@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=radu.nicolau@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).