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  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:	Thu, 21 Aug 2014 19:03:01 +0200
From:	Jiri Pirko <>
To:	Ben Hutchings <>
Subject: Re: [patch net-next RFC 03/12] net: introduce generic switch devices

Thu, Aug 21, 2014 at 06:41:23PM CEST, 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?

That is certainly possible. But so far, there is no need for it. But I
guess that it's probably a good idea at least to put it into sysfs

Noted, thanks 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