netdev - Re: [patch net-next RFC 0/4] introduce infrastructure for support of switch chip datapath

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: <CAGVrzcY5rhyu3KC2PQd0X+xdBB1D2yJhhPWntLRNoOhTSfDvoQ@mail.gmail.com>
Date:	Thu, 27 Mar 2014 14:54:11 -0700
From:	Florian Fainelli <f.fainelli@...il.com>
To:	Jamal Hadi Salim <jhs@...atatu.com>
Cc:	Sergey Ryazanov <ryazanov.s.a@...il.com>,
	Jiri Pirko <jiri@...nulli.us>,
	Roopa Prabhu <roopa@...ulusnetworks.com>,
	Neil Horman <nhorman@...driver.com>,
	Thomas Graf <tgraf@...g.ch>, netdev <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.net>,
	Andy Gospodarek <andy@...yhouse.net>,
	dborkman <dborkman@...hat.com>, ogerlitz <ogerlitz@...lanox.com>,
	jesse <jesse@...ira.com>, pshelar <pshelar@...ira.com>,
	azhou <azhou@...ira.com>, Ben Hutchings <ben@...adent.org.uk>,
	Stephen Hemminger <stephen@...workplumber.org>,
	jeffrey.t.kirsher@...el.com, vyasevic <vyasevic@...hat.com>,
	Cong Wang <xiyou.wangcong@...il.com>,
	John Fastabend <john.r.fastabend@...el.com>,
	Eric Dumazet <edumazet@...gle.com>,
	Scott Feldman <sfeldma@...ulusnetworks.com>,
	Lennert Buytenhek <buytenh@...tstofly.org>,
	Shrijeet Mukherjee <shm@...ulusnetworks.com>,
	Felix Fietkau <nbd@...nwrt.org>
Subject: Re: [patch net-next RFC 0/4] introduce infrastructure for support of
 switch chip datapath

2014-03-27 14:47 GMT-07:00 Jamal Hadi Salim <jhs@...atatu.com>:
> On 03/27/14 16:01, Florian Fainelli wrote:
>>
>> 2014-03-27 12:58 GMT-07:00 Sergey Ryazanov <ryazanov.s.a@...il.com>:
>>>
>>> 2014-03-27 20:55 GMT+04:00 Jiri Pirko <jiri@...nulli.us>:
>
>
>>> Moreover, we need to know ports of switch chip, what are really wired
>>> to the connectors (e.g. five-port switch on the board with only three
>>> connectors).
>>
>>
>> Well, DSA already does all of that for you and has Device Tree
>> bindings too to instantiate per-port net_device, create the switch
>> routing table in case switches are cascaded...
>>
>
> Just to be clear:
> routing here implies how the devices are interconnected (as opposed
> to L3 packet processing).

Correct, this is more like chaining here.

> Is that generic enough to be usable for different vendors or only
> specific to marvel?

I think it is. There is nothing in-tree that actually uses that
feature (switch chaining), but all the infrastructure is there to:

- represent links between switches, which one is cascaded from which
one and get a sense of their addressing within the switch tree
- a function call to get that cascading table to programmed to each switch
- get all relevant "uplink/downlink" switch ports to be configured appropriately
-- 
Florian
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html