From: Randy Dunlap <rdunlap@infradead.org>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v2] docs: net: document guidance of implementing the SR-IOV NDOs
Date: Wed, 19 Jun 2024 17:48:42 -0700 [thread overview]
Message-ID: <7dc51532-55b1-4f10-af8f-bf8a703e1874@infradead.org> (raw)
In-Reply-To: <20240620002741.1029936-1-kuba@kernel.org>
On 6/19/24 5:27 PM, Jakub Kicinski wrote:
> New drivers were prevented from adding ndo_set_vf_* callbacks
> over the last few years. This was expected to result in broader
> switchdev adoption, but seems to have had little effect.
>
> Based on recent netdev meeting there is broad support for allowing
> adding those ops.
>
> There is a problem with the current API supporting a limited number
> of VFs (100+, which is less than some modern HW supports).
> We can try to solve it by adding similar functionality on devlink
> ports, but that'd be another API variation to maintain.
> So a netlink attribute reshuffling is a more likely outcome.
>
> Document the guidance, make it clear that the API is frozen.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> v2:
> - edits from Randy
> v1: https://lore.kernel.org/all/20240618192818.554646-1-kuba@kernel.org/
>
> CC: corbet@lwn.net
> CC: rdunlap@infradead.org
> CC: linux-doc@vger.kernel.org
> ---
> Documentation/networking/index.rst | 1 +
> Documentation/networking/sriov.rst | 25 +++++++++++++++++++++++++
> 2 files changed, 26 insertions(+)
> create mode 100644 Documentation/networking/sriov.rst
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
--
~Randy
next prev parent reply other threads:[~2024-06-20 0:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 0:27 [PATCH net-next v2] docs: net: document guidance of implementing the SR-IOV NDOs Jakub Kicinski
2024-06-20 0:48 ` Randy Dunlap [this message]
2024-06-20 17:58 ` Simon Horman
2024-06-21 9:20 ` patchwork-bot+netdevbpf
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=7dc51532-55b1-4f10-af8f-bf8a703e1874@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).