DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: <dev@dpdk.org>, <vladimir.medvedkin@intel.com>
Subject: Re: [PATCH 1/3] net/iavf: support qinq insertion offload for scalar path
Date: Thu, 7 Aug 2025 14:35:08 +0100	[thread overview]
Message-ID: <aJSrjExzZPM0YQg8@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250619133658.13494-1-ciara.loftus@intel.com>

On Thu, Jun 19, 2025 at 01:36:56PM +0000, Ciara Loftus wrote:
> Enable Tx QINQ offload if the VF reports support for inserting both an
> outer and inner VLAN tag. The VF capabilities report the locations for
> placing each of the tags - either L2TAG1 in the tx descriptor or L2TAG2
> in the context descriptor. Use this information to configure the
> descriptors correctly.
> This offload was previously incorrectly reported as always supported in
> the device configuration, so this is corrected.
> 
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> ---
>  doc/guides/nics/features/iavf.ini    |  1 +
>  drivers/net/intel/iavf/iavf_ethdev.c |  8 +++-
>  drivers/net/intel/iavf/iavf_rxtx.c   | 55 +++++++++++++++++++++-------
>  3 files changed, 48 insertions(+), 16 deletions(-)
> 

Series-acked-by: Bruce Richardson <bruce.richardson@intel.com>

Applied to dpdk-next-net-intel.

Thanks,
/Bruce

      parent reply	other threads:[~2025-08-07 13:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 13:36 Ciara Loftus
2025-06-19 13:36 ` [PATCH 2/3] net/iavf: fix tx vector path selection logic Ciara Loftus
2025-06-19 13:36 ` [PATCH 3/3] net/iavf: support vlan insertion offload for the avx-512 path Ciara Loftus
2025-07-28 11:20 ` [PATCH 1/3] net/iavf: support qinq insertion offload for scalar path Bruce Richardson
2025-08-05 11:09   ` Loftus, Ciara
2025-08-07 13:35 ` Bruce Richardson [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=aJSrjExzZPM0YQg8@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=dev@dpdk.org \
    --cc=vladimir.medvedkin@intel.com \
    /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).