| 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: Mon, 5 Jul 2010 19:24:04 +0200 From: Lennert Buytenhek <buytenh@...tstofly.org> To: Joakim Tjernlund <joakim.tjernlund@...nsmode.se> Cc: netdev@...r.kernel.org Subject: Re: Distributed Switch Architecture(DSA) On Sun, Jun 20, 2010 at 04:41:31PM +0200, Joakim Tjernlund wrote: > > > If not, what is the point of DSA then if it doesn't use the native > > > forwarding capabilities of the HW switch? > > > > The point is and always was to provide a framework for proper integration > > of hardware switch chips into the Linux kernel. This framework doesn't > > become useless just because it doesn't already support every single > > hardware feature at this point. > > Right, sorry if I sounded a bit harsh. > > So DSA currently does a very minimal config of the HW switch to get > things going. Correct. > If you want to do something more fancy one has to > add a control plane to DSA which would possibly talk > to a user space app. Is that correct? Yes and no -- yes in the sense that if you want to use more functionality of the switch chip, you'll have to add some code that extracts that info from the Linux network interface config and turns it into commands for the switch chip, and no in the sense that I'm not sure yet what the best way to implement this would be. (Doing it all in userspace is one option.) -- 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