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, 19 Sep 2017 14:17:55 +0200 From: Andrew Lunn <andrew@...n.ch> To: Razvan Stefanescu <razvan.stefanescu@....com> Cc: gregkh@...uxfoundation.org, devel@...verdev.osuosl.org, ruxandra.radulescu@....com, arnd@...db.de, alexandru.marginean@....com, linux-kernel@...r.kernel.org, agraf@...e.de, stuyoder@...il.com, bogdan.purcareata@....com, linux-arm-kernel@...ts.infradead.org, laurentiu.tudor@....com Subject: Re: [PATCH 5/6] staging: fsl-dpaa2/ethsw: Add README On Tue, Sep 19, 2017 at 12:01:37PM +0300, Razvan Stefanescu wrote: > +Driver uses the switch device driver model and exposes each switch port as > +a network interface, which can be included in a bridge. Traffic switched > +between ports is offloaded into the hardware. Exposed network interfaces > +are not used for I/O, they are used just for configuration. This > +limitation is going to be addressed in the future. Hi Razvan Could you briefly describe how Ethernet frames get from the CPU to the switch. This is what decided if you should write a plain switchdev driver, or a DSA driver. Andrew
Powered by blists - more mailing lists