DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Radu Nicolau <radu.nicolau@intel.com>
Cc: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	 "Xing, Beilei" <beilei.xing@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 "stable@dpdk.org" <stable@dpdk.org>,
	Ferruh Yigit <ferruh.yigit@amd.com>,
	 Thomas Monjalon <thomas@monjalon.net>,
	Akhil Goyal <gakhil@marvell.com>
Subject: Re: [PATCH] net/iavf: fix Tx offloading flags check
Date: Tue, 24 Oct 2023 10:44:15 +0200	[thread overview]
Message-ID: <CAJFAV8xH614or8xeM=uj67F2zRuD3jgm+JMF9V6XqaHSTX=gjw@mail.gmail.com> (raw)
In-Reply-To: <f573b27a-be05-1da4-6be6-3943c30f9055@intel.com>

On Tue, Oct 24, 2023 at 10:40 AM Radu Nicolau <radu.nicolau@intel.com> wrote:
>
>
> On 24-Oct-23 6:42 AM, Zhang, Qi Z wrote:
> >
> >> -----Original Message-----
> >> From: Radu Nicolau <radu.nicolau@intel.com>
> >> Sent: Tuesday, October 24, 2023 12:38 AM
> >> To: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>
> >> Cc: dev@dpdk.org; Nicolau, Radu <radu.nicolau@intel.com>;
> >> stable@dpdk.org; Marchand, David <david.marchand@redhat.com>
> >> Subject: [PATCH] net/iavf: fix Tx offloading flags check
> >>
> >> Use IAVF_TX_OFFLOAD_MASK flags instead of
> >> IAVF_TX_CKSUM_OFFLOAD_MASK.
> >>
> >> Fixes: 3c715591ece0 ("net/iavf: fix checksum offloading")
> >> Cc: stable@dpdk.org
> >> Cc: david.marchand@redhat.com
> >>
> >> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
> >> ---
> >>   drivers/net/iavf/iavf_rxtx.c | 2 +-
> >>   1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/net/iavf/iavf_rxtx.c b/drivers/net/iavf/iavf_rxtx.c index
> >> c6ef6af1d8..85f8c141ce 100644
> >> --- a/drivers/net/iavf/iavf_rxtx.c
> >> +++ b/drivers/net/iavf/iavf_rxtx.c
> >> @@ -2664,7 +2664,7 @@ iavf_build_data_desc_cmd_offset_fields(volatile
> >> uint64_t *qw1,
> >>              l2tag1 |= m->vlan_tci;
> >>      }
> >>
> >> -    if ((m->ol_flags & IAVF_TX_CKSUM_OFFLOAD_MASK) == 0)
> >> +    if ((m->ol_flags & IAVF_TX_OFFLOAD_MASK) == 0)
> > Not sure if this will break previous fix.
> > Could you please provide some clarification regarding the specific offload flags that not in IAVF_TX_CKSUM_OFFLOAD_MASK, but you still don't want to skip?
>
> A specific flag is RTE_ETH_TX_OFFLOAD_SECURITY, and because this is not
> contained in IAVF_TX_OFFLOAD_MASK the previous fix broke the inline
> crypto feature.

RTE_ETH_TX_OFFLOAD_SECURITY is a ethdev level flag.
This is not supposed to be in a mbuf ol_flags, is it?



-- 
David Marchand


  reply	other threads:[~2023-10-24  8:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 16:38 Radu Nicolau
2023-10-24  5:42 ` Zhang, Qi Z
2023-10-24  8:39   ` Radu Nicolau
2023-10-24  8:44     ` David Marchand [this message]
2023-10-24  9:03       ` Radu Nicolau
2023-10-24  9:24         ` David Marchand
2023-10-25  9:12 ` [PATCH v2] " Radu Nicolau
2023-10-26  8:07   ` David Marchand
2023-10-30  0:19     ` 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='CAJFAV8xH614or8xeM=uj67F2zRuD3jgm+JMF9V6XqaHSTX=gjw@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=gakhil@marvell.com \
    --cc=jingjing.wu@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=radu.nicolau@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).