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]
Date:	Tue, 26 Aug 2014 19:45:44 -0700
From:	Tom Herbert <>
To:	Ben Hutchings <>
Cc:	Jiri Pirko <>,
	Linux Netdev List <>,
	David Miller <>,
	Neil Horman <>,,
	Thomas Graf <>,
	Daniel Borkmann <>,
	Or Gerlitz <>,
	Jesse Gross <>,
	Pravin B Shelar <>,
	Andy Zhou <>,
	Stephen Hemminger <>,
	Jeff Kirsher <>,, Cong Wang <>,
	John Fastabend <>,
	Eric Dumazet <>,
	Jamal Hadi Salim <>,
	Scott Feldman <>,
	Florian Fainelli <>,, John Linville <>,, Jason Wang <>,
	"Eric W. Biederman" <>,
	Nicolas Dichtel <>,, Lennert Buytenhek <>,, Felix Fietkau <>,
	Alexei Starovoitov <>,,
Subject: Re: [patch net-next RFC 03/12] net: introduce generic switch devices support

On Thu, Aug 21, 2014 at 9:41 AM, Ben Hutchings <> wrote:
> On Thu, 2014-08-21 at 18:18 +0200, Jiri Pirko wrote:
>> The goal of this is to provide a possibility to suport various switch
>> chips. Drivers should implement relevant ndos to do so. Now there is a
>> couple of ndos defines:
>> - for getting physical switch id is in place.
>> - for work with flows.
>> Note that user can use random port netdevice to access the switch.
> [...]
> Why isn't the switch treated as a real device (not necessarily a net
> device) that's included in the device model and that the port devices
> refer to?
+1. In the same way that software switch (e.g. OVS) is mostly
implemented out of the core stack, I think hardware switch should have
same model. Besides, if you define this as part of a network interface
then you'll need to resolve unpleasant issues like accounting for
bytes and packets switched (e.g. are these accounted in interface
stats?)), what happens if netdevice is put in promiscuous mode (e.g.
do we need a tap for all switched packets?), etc. Another thing to
consider is that some vendors will undoubtably implement an open flow
agent in the NIC to manage the switch, possibly even autonomously from
the host-- a host might see the device but not be able to manage it
other than adding interfaces as local ports.

> Ben.
> --
> Ben Hutchings
> If at first you don't succeed, you're doing about average.
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists