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  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:	Thu, 27 Mar 2014 14:54:11 -0700
From:	Florian Fainelli <>
To:	Jamal Hadi Salim <>
Cc:	Sergey Ryazanov <>,
	Jiri Pirko <>,
	Roopa Prabhu <>,
	Neil Horman <>,
	Thomas Graf <>, netdev <>,
	David Miller <>,
	Andy Gospodarek <>,
	dborkman <>, ogerlitz <>,
	jesse <>, pshelar <>,
	azhou <>, Ben Hutchings <>,
	Stephen Hemminger <>,, vyasevic <>,
	Cong Wang <>,
	John Fastabend <>,
	Eric Dumazet <>,
	Scott Feldman <>,
	Lennert Buytenhek <>,
	Shrijeet Mukherjee <>,
	Felix Fietkau <>
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 <>:
> On 03/27/14 16:01, Florian Fainelli wrote:
>> 2014-03-27 12:58 GMT-07:00 Sergey Ryazanov <>:
>>> 2014-03-27 20:55 GMT+04:00 Jiri Pirko <>:
>>> 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
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists