netdev - Re: [PATCH 0/4] RFC CPSW switchdev mode

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4277c55c-bea2-1061-35e9-62d1d0f60d28@ti.com>
Date:   Fri, 1 Jun 2018 16:29:08 -0500
From:   Grygorii Strashko <grygorii.strashko@...com>
To:     Ilias Apalodimas <ilias.apalodimas@...aro.org>,
        <netdev@...r.kernel.org>, <ivan.khoronzhuk@...aro.org>,
        <nsekhar@...com>, <jiri@...nulli.us>, <ivecera@...hat.com>
CC:     <francois.ozog@...aro.org>, <yogeshs@...com>, <spatton@...com>
Subject: Re: [PATCH 0/4] RFC CPSW switchdev mode

Hi Ilias,

On 05/24/2018 01:56 AM, Ilias Apalodimas wrote:
> Hello,
> 
> This is adding a new mode on the cpsw driver based around switchdev.
> In order to enable this you need to enable CONFIG_NET_SWITCHDEV,
> CONFIG_BRIDGE_VLAN_FILTERING, CONFIG_TI_CPSW_SWITCHDEV
> and add to udev config:
> 
> SUBSYSTEM=="net", ACTION=="add", ATTR{phys_switch_id}=="0f011900", \
>          ATTR{phys_port_name}!="", NAME="sw0$attr{phys_port_name}"
> Since the phys_switch_id is based on cpsw version, users with different
> version will need to do 'ip -d link show dev sw0p0 | grep switchid' and
> replace with the correct value.
> 
> This patch creates 3 ports, sw0p0, sw0p1 and sw0p2.
> sw0p1 and sw0p2 are the netdev interfaces connected to PHY devices
> while sw0p0 is the switch 'cpu facing port'.
> sw0p0 will be unable to receive and transmit traffic and it's not 100% within
> switchdev scope but, it's used to configure switch cpu port individually as
> this is needed for various switch features and configuration scenarios.

First, sorry for delayed reply it was very tough week (new SoC).

Second, Thanks a lot for your great work. I'm still testing it with different
 use cases and trying to consolidate my reply for all questions.

All, thanks for your comments.

-- 
regards,
-grygorii