[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191029113237.032c7851@cakuba.hsd1.ca.comcast.net>
Date: Tue, 29 Oct 2019 11:32:37 -0700
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Yuval Avnery <yuvalav@...lanox.com>
Cc: Andy Gospodarek <andrew.gospodarek@...adcom.com>,
Jiri Pirko <jiri@...nulli.us>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Jiri Pirko <jiri@...lanox.com>,
Saeed Mahameed <saeedm@...lanox.com>,
"leon@...nel.org" <leon@...nel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"shuah@...nel.org" <shuah@...nel.org>,
Daniel Jurgens <danielj@...lanox.com>,
Michael Chan <michael.chan@...adcom.com>
Subject: Re: [PATCH net-next 0/9] devlink vdev
On Tue, 29 Oct 2019 18:06:28 +0000, Yuval Avnery wrote:
> On 2019-10-29 10:08 a.m., Jakub Kicinski wrote:
> > On Fri, 25 Oct 2019 10:58:08 -0400, Andy Gospodarek wrote:
> >> # devlink vdev show pci/0000:03:00.0
> >> pci/0000:03:00.0/console/0: speed 115200 device /dev/ttySNIC0
> > The speed in this console example makes no sense to me.
> >
> > The patches as they stand are about the peer side/other side of the
> > port. So which side of the serial device is the speed set on? One can
> > just read the speed from /dev/ttySNIC0. And link that serial device to
> > the appropriate parent via sysfs. This is pure wheel reinvention.
> >
> The patches are not only about the other side,
>
> They are about all the devices which are under the control of a
> privileged user.
>
> In the case of SmartNic, those devices (vdevs) are on the host side, and
> the privileged user runs on the embedded CPU.
>
> The vdev devices don't necessarily have relationship with a port. All
> attributes are optional except flavour.
Okay, true, you can list the non-port PCIe functions. I should have
chosen my words more carefully.
Powered by blists - more mailing lists