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 for Android: free password hash cracker in your pocket

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

Message-ID: <20140326153155.GD12372@tuxdriver.com>
Date:	Wed, 26 Mar 2014 11:31:55 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Jamal Hadi Salim <jhs@...atatu.com>
Cc:	Roopa Prabhu <roopa@...ulusnetworks.com>,
	Florian Fainelli <f.fainelli@...il.com>,
	Neil Horman <nhorman@...driver.com>,
	Thomas Graf <tgraf@...g.ch>, Jiri Pirko <jiri@...nulli.us>,
	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>
Subject: Re: [patch net-next RFC 0/4] introduce infrastructure for support of
 switch chip datapath

On Wed, Mar 26, 2014 at 06:54:54AM -0400, Jamal Hadi Salim wrote:
> On 03/26/14 01:37, Roopa Prabhu wrote:

> >Most cases the switch port driver (API) can talk to the switch chip
> >driver without a switch netdev in between.
> >But there are cases where a switch netdev might become necessary for
> >switch chip specific operations (which probably has been discussed on
> >this thread). An example could be a global acl rule that applies to all
> >switch ports. One can argue that this can be applied on individual
> >switch ports and the switch driver can take care of consolidating or
> >optimally programming the acl rule in the switch chip.
> >
> 
> There are a lot of things which dont tie to a specific port.
> I think these should be transparent to the chip. If i add a route
> and the decision is for that route to go to the chip, then it
> shows up at the driver and it goes to the ASIC.
> If i am dumping a fib table and some parts of it sit in the chip,
> then whatever interfaces would end up querying the chip.

Right -- I think the netdev portions of the switch hardware drivers can
be made smart enough to handle most of this stuff behind the scenes.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
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