From: Jiri Pirko <jiri@resnulli.us>
To: Saeed Mahameed <saeedm@mellanox.com>
Cc: "jakub.kicinski@netronome.com" <jakub.kicinski@netronome.com>,
"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: Thu, 7 Nov 2019 11:24:25 +0100 [thread overview]
Message-ID: <20191107102425.GC2200@nanopsycho> (raw)
In-Reply-To: <c5bedde710b0667fd44213d8c64e65f6870a2f07.camel@mellanox.com>
Wed, Nov 06, 2019 at 11:21:37PM CET, saeedm@mellanox.com wrote:
>On Tue, 2019-11-05 at 17:38 -0800, Jakub Kicinski wrote:
>> On Tue, 5 Nov 2019 23:48:15 +0000, Saeed Mahameed wrote:
>> > On Tue, 2019-11-05 at 15:10 -0800, Jakub Kicinski wrote:
>> > > 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 :/
>> >
>> > I can say the same about netlink, it also was there, the missing
>> > part
>> > was the netlink ethtool connection and userspace parts ..
>>
>> uAPI is the part that matters. No driver implements all the APIs.
>> I'm telling you that the API for what you're trying to configure
>> already exists, and your driver should use it. Driver's technical
>> debt is not my concern.
>>
>> > Just because switchdev uAPI is powerful enough to do anything it
>> > doesn't mean we are ready, you said it, user space and drivers are
>> > not
>> > ready, and frankly it is not on the road map,
>>
>> I bet it's not on the road map. Product marketing sees only legacy
>> SR-IOV (table stakes) and OvS offload == switchdev (value add).
>> L2 switchdev will never be implemented with that mind set.
>>
>> In the upstream community, however, we care about the technical
>> aspects.
>>
>> > and we all know that it could take years before we can sit back and
>> > relax that we got our L2 switching ..
>>
>> Let's not be dramatic. It shouldn't take years to implement basic L2
>> switching offload.
>>
>> > Just like what is happening now with ethtool, it been years you
>> > know..
>>
>> Exactly my point!!! Nobody is going to lift a finger unless there is
>> a
>> loud and resounding "no".
>>
>
>Ok then, "no" new uAPI, although i still think there should be some
>special cases to be allowed, but ... your call.
>
>In the meanwhile i will figure out something to be driver only as
"something to be driver only". I'm curious what do you mean by that...
>intermediate solution until we have full l2 offload, then i can ask
>every one to move to full switchdev mode with a press of a button.
>
next prev parent reply other threads:[~2019-11-07 10:24 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
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 [this message]
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=20191107102425.GC2200@nanopsycho \
--to=jiri@resnulli.us \
--cc=dsahern@gmail.com \
--cc=jakub.kicinski@netronome.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).