netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Wei <dw@davidwei.uk>
Cc: netdev@vger.kernel.org, michael.chan@broadcom.com,
	andrew.gospodarek@broadcom.com, somnath.kotur@broadcom.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net v3 0/3] bnxt_en: support header page pool in queue API
Date: Thu, 05 Dec 2024 03:30:32 +0000	[thread overview]
Message-ID: <173336943226.1431012.12687765519874509231.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241204041022.56512-1-dw@davidwei.uk>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue,  3 Dec 2024 20:10:19 -0800 you wrote:
> Commit 7ed816be35ab ("eth: bnxt: use page pool for head frags") added a
> separate page pool for header frags. Now, frags are allocated from this
> header page pool e.g. rxr->tpa_info.data.
> 
> The queue API did not properly handle rxr->tpa_info and so using the
> queue API to i.e. reset any queues will result in pages being returned
> to the incorrect page pool, causing inflight != 0 warnings.
> 
> [...]

Here is the summary with links:
  - [net,v3,1/3] bnxt_en: refactor tpa_info alloc/free into helpers
    https://git.kernel.org/netdev/net/c/5883a3e0babf
  - [net,v3,2/3] bnxt_en: refactor bnxt_alloc_rx_rings() to call bnxt_alloc_rx_agg_bmap()
    https://git.kernel.org/netdev/net/c/bf1782d70ddd
  - [net,v3,3/3] bnxt_en: handle tpa_info in queue API implementation
    https://git.kernel.org/netdev/net/c/bd649c5cc958

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-12-05  3:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04  4:10 [PATCH net v3 0/3] bnxt_en: support header page pool in queue API David Wei
2024-12-04  4:10 ` [PATCH net v3 1/3] bnxt_en: refactor tpa_info alloc/free into helpers David Wei
2024-12-04  4:10 ` [PATCH net v3 2/3] bnxt_en: refactor bnxt_alloc_rx_rings() to call bnxt_alloc_rx_agg_bmap() David Wei
2024-12-04  4:10 ` [PATCH net v3 3/3] bnxt_en: handle tpa_info in queue API implementation David Wei
2024-12-10 12:25   ` Yunsheng Lin
2024-12-10 18:14     ` David Wei
2024-12-11 12:32       ` Yunsheng Lin
2024-12-11 16:10         ` David Wei
2024-12-11 17:11           ` Michael Chan
2024-12-12  0:48             ` Jakub Kicinski
2024-12-12 11:23               ` Yunsheng Lin
2024-12-12 14:56                 ` Jakub Kicinski
2024-12-13 12:17                   ` Yunsheng Lin
2024-12-31 11:49                     ` Yunsheng Lin
2024-12-16 21:41             ` David Wei
2024-12-16 22:48               ` Michael Chan
2024-12-16 22:59                 ` David Wei
2024-12-04 22:43 ` [PATCH net v3 0/3] bnxt_en: support header page pool in queue API Michael Chan
2024-12-05  3:30 ` patchwork-bot+netdevbpf [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=173336943226.1431012.12687765519874509231.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew.gospodarek@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=dw@davidwei.uk \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=somnath.kotur@broadcom.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).