netdev - Re: [PATCH 3/4] net: dsa: Associate slave network device with CPU port

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: <87vanzbsjd.fsf@weeman.i-did-not-set--mail-host-address--so-tickle-me>
Date:   Tue, 13 Jun 2017 15:23:50 -0400
From:   Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To:     Florian Fainelli <f.fainelli@...il.com>, netdev@...r.kernel.org
Cc:     davem@...emloft.net, andrew@...n.ch, john@...ozen.org,
        Florian Fainelli <f.fainelli@...il.com>
Subject: Re: [PATCH 3/4] net: dsa: Associate slave network device with CPU port

Florian Fainelli <f.fainelli@...il.com> writes:

> In preparation for supporting multiple CPU ports with DSA, have the
> dsa_port structure know which CPU it is associated with. This will be
> important in order to make sure the correct CPU is used for transmission
> of the frames. If not for functional reasons, for performance (e.g: load
> balancing) and forwarding decisions.
>
> Signed-off-by: Florian Fainelli <f.fainelli@...il.com>

Reviewed-by: Vivien Didelot <vivien.didelot@...oirfairelinux.com>