From: patchwork-bot+netdevbpf@kernel.org
To: Parav Pandit <parav@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, corbet@lwn.net,
dw@davidwei.uk, kalesh-anakkur.purayil@broadcom.com,
saeedm@nvidia.com, leon@kernel.org, jiri@resnulli.us,
shayd@nvidia.com, danielj@nvidia.com, dchumak@nvidia.com,
linux-doc@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [net-next v4 0/2] devlink: Add port function attribute for IO EQs
Date: Mon, 08 Apr 2024 13:20:26 +0000 [thread overview]
Message-ID: <171258242694.15799.9946974100091774097.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240406010538.220167-1-parav@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Sat, 6 Apr 2024 04:05:36 +0300 you wrote:
> Currently, PCI SFs and VFs use IO event queues to deliver netdev per
> channel events. The number of netdev channels is a function of IO
> event queues. In the second scenario of an RDMA device, the
> completion vectors are also a function of IO event queues. Currently, an
> administrator on the hypervisor has no means to provision the number
> of IO event queues for the SF device or the VF device. Device/firmware
> determines some arbitrary value for these IO event queues. Due to this,
> the SF netdev channels are unpredictable, and consequently, the
> performance is too.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/2] devlink: Support setting max_io_eqs
https://git.kernel.org/netdev/net-next/c/5af3e3876d56
- [net-next,v4,2/2] mlx5/core: Support max_io_eqs for a function
https://git.kernel.org/netdev/net-next/c/93197c7c509d
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-08 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 1:05 [net-next v4 0/2] devlink: Add port function attribute for IO EQs Parav Pandit
2024-04-06 1:05 ` [net-next v4 1/2] devlink: Support setting max_io_eqs Parav Pandit
2024-04-06 1:05 ` [net-next v4 2/2] mlx5/core: Support max_io_eqs for a function Parav Pandit
2024-04-07 16:08 ` David Wei
2024-04-08 12:44 ` Jiri Pirko
2024-04-06 9:05 ` [net-next v4 0/2] devlink: Add port function attribute for IO EQs Zhu Yanjun
2024-04-08 3:20 ` Parav Pandit
2024-04-08 13:20 ` 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=171258242694.15799.9946974100091774097.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corbet@lwn.net \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=dchumak@nvidia.com \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.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