From: patchwork-bot+netdevbpf@kernel.org
To: Ziwei Xiao <ziweixiao@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, jeroendb@google.com,
pkaligineedi@google.com, shailend@google.com, willemb@google.com,
hramamurthy@google.com, rushilg@google.com, jfraker@google.com,
junfeng.guo@intel.com, Julia.Lawall@inria.fr, horms@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] gve: Remove qpl_cfg struct since qpl_ids map with queues respectively
Date: Fri, 19 Apr 2024 01:50:29 +0000 [thread overview]
Message-ID: <171349142992.11062.2278804601434624598.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240417205757.778551-1-ziweixiao@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 17 Apr 2024 20:57:57 +0000 you wrote:
> The qpl_cfg struct was used to make sure that no two different queues
> are using QPL with the same qpl_id. We can remove that qpl_cfg struct
> since now the qpl_ids map with the queues respectively as follows:
> For tx queues: qpl_id = tx_qid
> For rx queues: qpl_id = max_tx_queues + rx_qid
>
> And when XDP is used, it will need the user to reduce the tx queues to
> be at most half of the max_tx_queues. Then it will use the same number
> of tx queues starting from the end of existing tx queues for XDP. So the
> XDP queues will not exceed the max_tx_queues range and will not overlap
> with the rx queues, where the qpl_ids will not have overlapping too.
>
> [...]
Here is the summary with links:
- [net-next] gve: Remove qpl_cfg struct since qpl_ids map with queues respectively
https://git.kernel.org/netdev/net-next/c/fdf412374379
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-04-19 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 20:57 [PATCH net-next] gve: Remove qpl_cfg struct since qpl_ids map with queues respectively Ziwei Xiao
2024-04-19 1: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=171349142992.11062.2278804601434624598.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Julia.Lawall@inria.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=jfraker@google.com \
--cc=junfeng.guo@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=rushilg@google.com \
--cc=shailend@google.com \
--cc=willemb@google.com \
--cc=ziweixiao@google.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