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:   Fri, 27 Nov 2020 01:55:02 +0100
From:   Andrew Lunn <>
To:     Lukasz Majewski <>
Cc:     Vladimir Oltean <>,
        Fugang Duan <>,
        "David S . Miller" <>,
        Jakub Kicinski <>,,
        Fabio Estevam <>,
        Vivien Didelot <>,
        NXP Linux Team <>,
        Florian Fainelli <>,,,
        Peng Fan <>,,, Shawn Guo <>
Subject: Re: [RFC 0/4] net: l2switch: Provide support for L2 switch on i.MX28

> (A side question - DSA uses switchdev, so when one shall use switchdev
> standalone?)

DSA gives you a framework for an Ethernet switch connected to a host
via Ethernet for the data plane. Generally, that Ethernet link to the
switch is a MAC to MAC connection. It can be PHY to PHY. But those are
just details. The important thing is you use an Ethernet driver on the

If you look at pure switchdev devices, they generally DMA frames
directly into the switch. There is either one DMA queue per switch
port, or there is a way to multiplex frames over one DMA queue,
generally by additional fields in the buffer descriptor.

For this device, at the moment, it is hard to say which is the best
fit. A lot will depend on how the FEC driver works, if you can reuse
it, while still having the degree of control you need over the DMA
channel. If you can reuse the FEC driver, then a DSA driver might
work. If the coupling it too loose, and you have to take control of
the DMA, then a pure switchdev driver seems more appropriate.


Powered by blists - more mailing lists