[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<171258242694.15799.9946974100091774097.git-patchwork-notify@kernel.org>
Date: Mon, 08 Apr 2024 13:20:26 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Parav Pandit <parav@...dia.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, corbet@....net, dw@...idwei.uk,
kalesh-anakkur.purayil@...adcom.com, saeedm@...dia.com, leon@...nel.org,
jiri@...nulli.us, shayd@...dia.com, danielj@...dia.com, dchumak@...dia.com,
linux-doc@...r.kernel.org, linux-rdma@...r.kernel.org
Subject: Re: [net-next v4 0/2] devlink: Add port function attribute for IO EQs
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.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
Powered by blists - more mailing lists