netdev - Re: [RFC PATCH net-next 0/2] Add new switchdev device class

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20150827.162503.1483675558033304575.davem@davemloft.net>
Date:	Thu, 27 Aug 2015 16:25:03 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	sfeldma@...il.com
Cc:	netdev@...r.kernel.org, jiri@...nulli.us, f.fainelli@...il.com,
	roopa@...ulusnetworks.com
Subject: Re: [RFC PATCH net-next 0/2] Add new switchdev device class

From: sfeldma@...il.com
Date: Thu, 27 Aug 2015 00:16:44 -0700

> Comments?

No fundamental objections from me.

I just want to reiterate one thing I think Jiri said.

There are other kinds of devices which make up this kind of hierarchy.
I can think of two examples involving bonafide ethernet ports.

1) A top-level parent device provides the resources for all of the RX
   and TX queues, which are allocated and divided by the driver down into
   the ethernet ports below.  Example: niu

2) Cards are going to need more than one PCI-E slot to get all of the
   PCI-E lanes necessary to saturate the link.  Two PCI devices
   show up and need to get probed in this scenerio and it would be
   nice to have some object to represent the logical "glueing"
   together of those two devices.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html