lkml.org 
[lkml]   [2021]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC 0/4] net: l2switch: Provide support for L2 switch on i.MX28 SoC
    On Thu, Jun 17, 2021 at 01:08:21PM +0200, Lukasz Majewski wrote:
    > Hi Andrew,
    >
    > > > > I would push back and say that the switch offers bridge
    > > > > acceleration for the FEC.
    > > >
    > > > Am I correct, that the "bridge acceleration" means in-hardware
    > > > support for L2 packet bridging?
    > >
    > > You should think of the hardware as an accelerator, not a switch. The
    > > hardware is there to accelerate what linux can already do. You setup a
    > > software bridge in linux, and then offload L2 switching to the
    > > accelerator. You setup vlans in linux, and then offload the filtering
    > > of them to the accelerator. If there is something linux can do, but
    > > the hardware cannot accelerate, you leave linux to do it in software.
    > >
    > > > Do you propose to catch some kind of notification when user calls:
    > > >
    > > > ip link add name br0 type bridge; ip link set br0 up;
    > > > ip link set lan1 up; ip link set lan2 up;
    > > > ip link set lan1 master br0; ip link set lan2 master br0;
    > > > bridge link
    >
    > ^^^^^^^^^^^^^ [*]
    >
    > > >
    > > > And then configure the FEC driver to use this L2 switch driver?
    > >
    > > That is what switchdev does. There are various hooks in the network
    > > stack which call into switchdev to ask it to offload operations to the
    > > accelerator.
    >
    > I'm a bit confused about the interfaces that pop up when I do enable
    > bridging acceleration.
    >
    > Without bridge I do have:
    > - eth0 (this is a 'primary' interface -> it also controls MII/PHY for
    > eth1)
    > - eth1 (it uses the MII/PHY control from eth0)

    You need to be careful with wording here. eth0 might provide an MDIO
    bus which eth1 PHY is connected to, but eth1 is controlling the PHY,
    not eth0.

    >
    > Both interfaces works correctly.
    >
    > And after starting the bridge (and switchdev) with commands from [*] I
    > do have:

    You don't start switchdev. switchdev is just an API between the
    network stack and the hardware accelerator.

    > - br0 (created bridge - need to assign IP to it to communicate outside,
    > even when routing is set via eth0, and eth0 has the same IP address)

    The IP address should only be on the bridge.

    > - eth0 (just is used to control PHY - ifconfig up/down)
    > - eth1 (just is used to control PHY - ifconfig up/down)

    It is more than that. You can still send on these interfaces. e.g. if
    you are using ldap, or L2 PTP, the daemons will use these interfaces,
    not the bridge, since they want to send frames out a specific
    interface.

    > And now the question, how internally shall I tackle the transmission
    > (i.e. DMA setups)?
    >
    > Now, I do use some hacks to re-use code for eth0 to perform the
    > transmission from/to imx28 L2 switch.

    Avoid hacks. Always. Step back. Look at the hardware. How is the
    hardware meant to be used when using the switch?

    You have two choices.

    1) A DSA style driver. The SoC has an Ethernet interface connect to
    one port of the switch. In this case, there should be two additional
    ports of the switch connected to the outside world, i.e. the switch
    has 3 ports.

    2) A pure switchdev driver. You DMA frames directly to the switch
    ingree/egress queues for each port connected to the outside world. In
    this case, you have a 2 port switch.

    Once you get the architecture correct, then you can think about the
    driver. Maybe you can reuse parts of the FEC? Maybe not.

    Andrew

    \
     
     \ /
      Last update: 2021-06-17 15:59    [W:39.159 / U:0.004 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site