From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Saeed Mahameed <saeedm@mellanox.com>
Cc: "sbrivio@redhat.com" <sbrivio@redhat.com>,
"nikolay@cumulusnetworks.com" <nikolay@cumulusnetworks.com>,
"dsahern@gmail.com" <dsahern@gmail.com>,
"sd@queasysnail.net" <sd@queasysnail.net>,
Jiri Pirko <jiri@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
Ariel Levkovich <lariel@mellanox.com>
Subject: Re: [PATCH net-next v2 0/3] VGT+ support
Date: Tue, 5 Nov 2019 15:10:31 -0800 [thread overview]
Message-ID: <20191105151031.1e7c6bbc@cakuba.netronome.com> (raw)
In-Reply-To: <8c740914b7627a10e05313393442d914a42772d1.camel@mellanox.com>
On Tue, 5 Nov 2019 22:52:18 +0000, Saeed Mahameed wrote:
> > > it should be just like ethtool we want to to replace it but we know
> > > we are not there yet, so we carefully add only necessary things
> > > with
> > > lots of auditing, same should go here.
> >
> > Worked out amazingly for ethtool, right?
>
> Obviously, no one would have agreed to such total shutdown for ethtool,
> we eventually decided not to block ethtool unless we have the netlink
> adapter working .. legacy mode should get the same treatment.
>
> Bottom line for the same reason we decided that ethtool is not totally
> dead until ethtool netlink interface is complete, we should still
> support selective and basic sriov legacy mode extensions until bridge
> offloads is complete.
But switchdev _is_ _here_. _Today_. From uAPI perspective it's done,
and ready. We're missing the driver and user space parts, but no core
and uAPI extensions. It's just L2 switching and there's quite a few
switch drivers upstream, as I'm sure you know :/
ethtool is not ready from uAPI perspective, still.
It'd be more accurate to compare to legacy IOCTLs, like arguing that
we need a small tweak to IOCTLs when Netlink is already there..
next prev parent reply other threads:[~2019-11-05 23:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 19:47 [PATCH net-next v2 0/3] VGT+ support Ariel Levkovich
2019-10-31 19:47 ` [PATCH net-next v2 1/3] net: Support querying specific VF properties Ariel Levkovich
2019-10-31 19:47 ` [PATCH net-next v2 2/3] net: Add SRIOV VGT+ support Ariel Levkovich
2019-10-31 19:47 ` [PATCH net-next v2 3/3] net/mlx5: " Ariel Levkovich
2019-10-31 20:31 ` [PATCH net-next v2 0/3] " David Miller
2019-10-31 22:20 ` Ariel Levkovich
2019-10-31 22:58 ` David Miller
2019-11-01 14:55 ` Ariel Levkovich
2019-11-01 0:23 ` Jakub Kicinski
[not found] ` <8d7db56c-376a-d809-4a65-bfc2baf3254f@mellanox.com>
2019-11-01 21:28 ` Saeed Mahameed
2019-11-02 0:21 ` Jakub Kicinski
2019-11-05 1:38 ` Saeed Mahameed
2019-11-05 1:47 ` David Ahern
2019-11-05 2:35 ` Jakub Kicinski
2019-11-05 20:10 ` Saeed Mahameed
2019-11-05 21:55 ` Jakub Kicinski
2019-11-05 22:52 ` Saeed Mahameed
2019-11-05 23:10 ` Jakub Kicinski [this message]
2019-11-05 23:48 ` Saeed Mahameed
2019-11-06 1:38 ` Jakub Kicinski
2019-11-06 22:21 ` Saeed Mahameed
2019-11-07 10:24 ` Jiri Pirko
2019-11-13 22:55 ` Keller, Jacob E
2019-11-14 2:25 ` Jakub Kicinski
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=20191105151031.1e7c6bbc@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=dsahern@gmail.com \
--cc=jiri@mellanox.com \
--cc=lariel@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=saeedm@mellanox.com \
--cc=sbrivio@redhat.com \
--cc=sd@queasysnail.net \
--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).