| 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: Tue, 13 Jan 2009 11:54:07 -0500 From: Robin Getz <rgetz@...ckfin.uclinux.org> To: "Florian Fainelli" <florian@...nwrt.org> Cc: netdev@...r.kernel.org Subject: Re: 802.1Q support? On Tue 13 Jan 2009 08:29, Florian Fainelli pondered: > Le Tuesday 13 January 2009 13:31:20 Robin Getz, vous avez écrit : > > Great - That looks like the way to go -- is there any plan in sending this > > to mainline? > > Yes we will definitively submit it for mainline inclusion, Felix, who wrote > the swconfig stuff will probably want to clean it up a bit and/or add > features. > > Lennert Buytenhek also proposed a Distributed Switch Architecture which is > worth looking at, though it does not cover more "classical" switches > connection over GPIO, SPI or special PHY address. Hmmm ... https://kerneltrap.org/mailarchive/linux-netdev/2008/9/25/3411164/thread > The switch driver presents each port on the switch as a separate > network interface to Linux, polls the switch to maintain software > link state of those ports, forwards MII management interface > accesses to those network interfaces (e.g. as done by ethtool) to > the switch, and exposes the switch's hardware statistics counters > via the appropriate Linux kernel interfaces. This exposes eth[n] for every port - and these are managed by the standard userspace tools? That seems like it would be more intuitive for end users -- wouldn't it? -- 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