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 17:59:56 -0400
From:	Jamal Hadi Salim <>
To:	Florian Fainelli <>
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

On 03/27/14 17:54, Florian Fainelli wrote:
> 2014-03-27 14:47 GMT-07:00 Jamal Hadi Salim <>:

> 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

Sounds like we have a winner on this aspect at least.
Is it a common setup to have such cascading though - or is this some
overzelous way of solving cascading switches within a LAN?

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