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>
Subject: Re: [PATCH 0/3] Fixes for iavf Tx path selection
Date: Thu, 4 Sep 2025 18:18:12 +0100	[thread overview]
Message-ID: <aLnJ1M4jt8OM8HhV@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250904104440.2167205-1-ciara.loftus@intel.com>

On Thu, Sep 04, 2025 at 10:44:37AM +0000, Ciara Loftus wrote:
> This is a series of fixes for the iavf driver concerning Tx path
> selection. The first patch fixes the logic for selecting the Tx
> vector path, which was recently fixed but broken again by another
> commit. The second patch updates a log and the third ensures the
> fastest path is selected for VLAN offload regardless of VLAN tag
> location (L2TAG1 or L2TAG2).
> 
> Ciara Loftus (3):
>   net/iavf: fix Tx vector path selection logic again
>   net/iavf: fix a log during Tx path selection
>   net/iavf: fix Tx path selection for VLAN offload
> 
>  drivers/net/intel/iavf/iavf_rxtx.c            |  4 ++--
>  drivers/net/intel/iavf/iavf_rxtx.h            |  1 -
>  drivers/net/intel/iavf/iavf_rxtx_vec_common.h | 23 +++++++++++--------
>  3 files changed, 15 insertions(+), 13 deletions(-)
> 
> --

Series applied and squashed into next-net-intel

/Bruce

      parent reply	other threads:[~2025-09-04 17:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 10:44 Ciara Loftus
2025-09-04 10:44 ` [PATCH 1/3] net/iavf: fix Tx vector path selection logic again Ciara Loftus
2025-09-04 16:59   ` Bruce Richardson
2025-09-04 10:44 ` [PATCH 2/3] net/iavf: fix a log during Tx path selection Ciara Loftus
2025-09-04 17:00   ` Bruce Richardson
2025-09-04 10:44 ` [PATCH 3/3] net/iavf: fix Tx path selection for VLAN offload Ciara Loftus
2025-09-04 17:10   ` Bruce Richardson
2025-09-04 17:18 ` 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=aLnJ1M4jt8OM8HhV@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=dev@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).