From: Yuval Avnery <yuvalav@mellanox.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Jiri Pirko <jiri@mellanox.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Gospodarek <andy@greyhouse.net>,
Daniel Jurgens <danielj@mellanox.com>,
Parav Pandit <parav@mellanox.com>
Subject: RE: [PATCH net-next] netdevsim: Add max_vfs to bus_dev
Date: Mon, 16 Dec 2019 22:52:30 +0000 [thread overview]
Message-ID: <AM6PR05MB5142B1D44D6190BBDE19F7E0C5510@AM6PR05MB5142.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20191216124441.634ea8ea@cakuba.netronome.com>
> -----Original Message-----
> From: Jakub Kicinski <jakub.kicinski@netronome.com>
> Sent: Monday, December 16, 2019 12:45 PM
> To: Yuval Avnery <yuvalav@mellanox.com>
> Cc: Jiri Pirko <jiri@mellanox.com>; davem@davemloft.net;
> netdev@vger.kernel.org; linux-kernel@vger.kernel.org; Andy Gospodarek
> <andy@greyhouse.net>; Daniel Jurgens <danielj@mellanox.com>
> Subject: Re: [PATCH net-next] netdevsim: Add max_vfs to bus_dev
>
> The ip-link API will suddenly start returning errors which may not be
> expected to the user space. So the question is what the user space is you're
> expecting to run/testing with? _Some_ user space should prove this design
> out before we merge it.
>
> The alternative design is to "forward" hosts ip-link requests to the NIC CPU
> and let software running there talk to the cloud back end.
> Rather than going
> customer -> could API -> NIC,
> go
> customer -> NIC -> cloud API
> That obviously is more complex, but has the big advantage of nothing on the
> host CPU having to change.
I will try to summarize your comments:
1. There will always be encapsulation, therefore network management shouldn't care what MACs customers use.
2. Customer is always requesting MAC, it never simply acquires it from the NIC.
There is always going to be an entity running on the host setting MACs to VFs.
Is that correct?
next prev parent reply other threads:[~2019-12-16 22:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 2:58 [PATCH net-next] netdevsim: Add max_vfs to bus_dev Yuval Avnery
2019-12-11 17:58 ` Jakub Kicinski
2019-12-11 18:19 ` Yuval Avnery
2019-12-11 19:15 ` Jakub Kicinski
2019-12-11 19:57 ` Yuval Avnery
2019-12-11 22:24 ` Jakub Kicinski
2019-12-11 23:25 ` Yuval Avnery
2019-12-11 23:49 ` Jakub Kicinski
2019-12-12 5:11 ` Yuval Avnery
2019-12-12 18:25 ` Jakub Kicinski
2019-12-12 18:47 ` Ido Schimmel
2019-12-13 1:37 ` Jakub Kicinski
2019-12-12 20:44 ` Yuval Avnery
2019-12-13 1:54 ` Jakub Kicinski
2019-12-13 3:21 ` Yuval Avnery
2019-12-13 18:08 ` Jakub Kicinski
2019-12-13 20:05 ` Yuval Avnery
2019-12-16 20:44 ` Jakub Kicinski
2019-12-16 22:52 ` Yuval Avnery [this message]
2019-12-17 19:06 ` Yuval Avnery
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=AM6PR05MB5142B1D44D6190BBDE19F7E0C5510@AM6PR05MB5142.eurprd05.prod.outlook.com \
--to=yuvalav@mellanox.com \
--cc=andy@greyhouse.net \
--cc=danielj@mellanox.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=parav@mellanox.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).