All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Taehee Yoo <ap420073@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, michael.chan@broadcom.com,
	netdev@vger.kernel.org, somnath.kotur@broadcom.com,
	dw@davidwei.uk, horms@kernel.org
Subject: Re: [PATCH net v2] bnxt_en: update xdp_rxq_info in queue restart logic
Date: Thu, 25 Jul 2024 14:50:34 +0000	[thread overview]
Message-ID: <172191903420.31720.11517062632371090454.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240721053554.1233549-1-ap420073@gmail.com>

Hello:

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

On Sun, 21 Jul 2024 05:35:54 +0000 you wrote:
> When the netdev_rx_queue_restart() restarts queues, the bnxt_en driver
> updates(creates and deletes) a page_pool.
> But it doesn't update xdp_rxq_info, so the xdp_rxq_info is still
> connected to an old page_pool.
> So, bnxt_rx_ring_info->page_pool indicates a new page_pool, but
> bnxt_rx_ring_info->xdp_rxq is still connected to an old page_pool.
> 
> [...]

Here is the summary with links:
  - [net,v2] bnxt_en: update xdp_rxq_info in queue restart logic
    https://git.kernel.org/netdev/net/c/b537633ce57b

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-07-25 14:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-21  5:35 [PATCH net v2] bnxt_en: update xdp_rxq_info in queue restart logic Taehee Yoo
2024-07-21 16:57 ` David Wei
2024-07-23 10:59 ` Paolo Abeni
2024-07-23 17:37   ` Taehee Yoo
2024-07-23 15:42 ` Brett Creeley
2024-07-23 17:58   ` Taehee Yoo
2024-07-23 19:47     ` Brett Creeley
2024-07-25  5:00 ` Taehee Yoo
2024-07-25  5:45 ` Somnath Kotur
2024-07-25 14:50 ` 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=172191903420.31720.11517062632371090454.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ap420073@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dw@davidwei.uk \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.