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
| ||
|
Date: Sat, 25 Oct 2014 20:00:16 +0200 From: Andrew Lunn <andrew@...n.ch> To: Florian Fainelli <f.fainelli@...il.com> Cc: Andrew Lunn <andrew@...n.ch>, Guenter Roeck <linux@...ck-us.net>, netdev <netdev@...r.kernel.org>, "David S. Miller" <davem@...emloft.net>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 06/14] net: dsa: Add support for hardware monitoring On Sat, Oct 25, 2014 at 10:23:27AM -0700, Florian Fainelli wrote: > On 10/25/14 07:01, Andrew Lunn wrote: > >> Here is another naming option: > >> > >> em1dsa0-virtual-0 > > > > I prefer this over isa. > > > > However, i think there should be some sort of separator between the > > network device name and dsa. > > Considering that network devices can be renamed, do we want it to be > included in the sensor name at all? Well, we need something which identifies the "DSA collection". In that, you could have two or more collections, connected to different network devices. I once came across a PCI board with two Intel ethernet chipsets and two 10 port Marvell switches. Each switch had one host cpu port, 3 ports interconnected to the other switch, and 6 going to the back panel. You would want to describe that as two separate DSA entities, not one DSA with two switches. So the name needs something to indicate the DSA collection. Andrew -- 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
Powered by blists - more mailing lists