From: patchwork-bot+netdevbpf@kernel.org
To: Parav Pandit <parav@nvidia.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org,
stephen@networkplumber.org, jiri@nvidia.com, shayd@nvidia.com
Subject: Re: [PATCH v2 0/2] devlink: Support setting max_io_eqs
Date: Sat, 13 Apr 2024 16:40:27 +0000 [thread overview]
Message-ID: <171302642714.24529.12887628327943229659.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240410115808.12896-1-parav@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Wed, 10 Apr 2024 14:58:06 +0300 you wrote:
> Devices send event notifications for the IO queues,
> such as tx and rx queues, through event queues.
>
> Enable a privileged owner, such as a hypervisor PF, to set the number
> of IO event queues for the VF and SF during the provisioning stage.
>
> example:
> Get maximum IO event queues of the VF device::
>
> [...]
Here is the summary with links:
- [v2,1/2] uapi: Update devlink kernel headers
(no matching commit)
- [v2,2/2] devlink: Support setting max_io_eqs
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=e8add23c59b7
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-13 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 11:58 [PATCH v2 0/2] devlink: Support setting max_io_eqs Parav Pandit
2024-04-10 11:58 ` [PATCH v2 1/2] uapi: Update devlink kernel headers Parav Pandit
2024-04-10 11:58 ` [PATCH v2 2/2] devlink: Support setting max_io_eqs Parav Pandit
2024-04-10 23:22 ` [PATCH v2 0/2] " Samudrala, Sridhar
2024-04-11 2:32 ` Parav Pandit
2024-04-11 23:03 ` Samudrala, Sridhar
2024-04-12 2:06 ` David Ahern
2024-04-12 3:31 ` Parav Pandit
2024-04-12 5:22 ` Parav Pandit
2024-04-12 22:03 ` Samudrala, Sridhar
2024-04-13 2:01 ` Parav Pandit
2024-04-13 16:40 ` 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=171302642714.24529.12887628327943229659.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@kernel.org \
--cc=jiri@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=shayd@nvidia.com \
--cc=stephen@networkplumber.org \
/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).