DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v1 00/15] IXGBE fixes and cleanups
Date: Wed, 6 May 2026 11:27:54 +0100	[thread overview]
Message-ID: <afsXqqXeM4djy3oC@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <afsJhAV6DLiLnWWy@bricha3-mobl1.ger.corp.intel.com>

On Wed, May 06, 2026 at 10:27:32AM +0100, Bruce Richardson wrote:
> On Thu, Apr 30, 2026 at 12:14:29PM +0100, Anatoly Burakov wrote:
> > This patchset fixes a bunch of very old issues in flow management
> > in IXGBE driver, such as:
> > 
> > - storing process-local pointers in shared memory
> > - incorrect L4 protocol matching for FDIR
> > - wrong handling of SCTP flow items
> > - reading stale FDIR state after flow destroy/flush
> > - storing all flows in global lists
> > 
> > In addition, some cleanup is also performed - refactors, moving
> > things around to avoid accessing process-local state, and
> > writing read-only values at init instead of deep in FDIR.
> > 
> > Finally, FDIR was also rejecting protocol-only matches for TCP
> > and UDP, these are now supported.
> > 
> > Depends on flow dump patchset: https://patches.dpdk.org/project/dpdk/list/?series=38016
> > 
> > Anatoly Burakov (15):
> >   net/ixgbe: fix flows not being scoped to port
> >   net/ixgbe: fix shared PF pointer in representor
> >   net/ixgbe: fix non-shared data in IPsec session
> >   net/ixgbe: fix SCTP protocol-only flow parsing
> >   net/ixgbe: fix L4 protocol mask handling
> >   net/ixgbe: reset flow state on clear paths
> >   net/ixgbe: store max VFs in adapter
> >   net/ixgbe: do not use flow list to count flows
> >   net/ixgbe: remove redundant flow tracking lists
> >   net/ixgbe: reduce FDIR conf macro usage
> >   net/ixgbe: use adapter in flow-related calls
> >   net/ixgbe: support protocol-only TCP and UDP rules
> >   net/ixgbe: write drop queue at init
> >   net/ixgbe: rely less on global flow state
> >   net/ixgbe: refactor flow creation
> > 
> Some good cleanups, thanks.
> 
> Series-Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Series applied to dpdk-next-net-intel.

Thanks,
/Bruce

      reply	other threads:[~2026-05-06 10:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 11:14 [PATCH v1 00/15] IXGBE fixes and cleanups Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 01/15] net/ixgbe: fix flows not being scoped to port Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 02/15] net/ixgbe: fix shared PF pointer in representor Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 03/15] net/ixgbe: fix non-shared data in IPsec session Anatoly Burakov
2026-05-07 10:50   ` Radu Nicolau
2026-04-30 11:14 ` [PATCH v1 04/15] net/ixgbe: fix SCTP protocol-only flow parsing Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 05/15] net/ixgbe: fix L4 protocol mask handling Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 06/15] net/ixgbe: reset flow state on clear paths Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 07/15] net/ixgbe: store max VFs in adapter Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 08/15] net/ixgbe: do not use flow list to count flows Anatoly Burakov
2026-05-06  9:24   ` Bruce Richardson
2026-04-30 11:14 ` [PATCH v1 09/15] net/ixgbe: remove redundant flow tracking lists Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 10/15] net/ixgbe: reduce FDIR conf macro usage Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 11/15] net/ixgbe: use adapter in flow-related calls Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 12/15] net/ixgbe: support protocol-only TCP and UDP rules Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 13/15] net/ixgbe: write drop queue at init Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 14/15] net/ixgbe: rely less on global flow state Anatoly Burakov
2026-04-30 11:14 ` [PATCH v1 15/15] net/ixgbe: refactor flow creation Anatoly Burakov
2026-05-06  9:27 ` [PATCH v1 00/15] IXGBE fixes and cleanups Bruce Richardson
2026-05-06 10:27   ` 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=afsXqqXeM4djy3oC@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@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