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: <20140402200639.GD3301@tuxdriver.com>
Date:	Wed, 2 Apr 2014 16:06:39 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Scott Feldman <sfeldma@...ulusnetworks.com>
Cc:	Andy Gospodarek <andy@...yhouse.net>,
	Jiri Pirko <jiri@...nulli.us>,
	Roopa Prabhu <roopa@...ulusnetworks.com>,
	Jamal Hadi Salim <jhs@...atatu.com>,
	Florian Fainelli <f.fainelli@...il.com>,
	Neil Horman <nhorman@...driver.com>,
	Thomas Graf <tgraf@...g.ch>, netdev <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.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>,
	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, Apr 02, 2014 at 12:54:50PM -0700, Scott Feldman wrote:
> 
> On Apr 2, 2014, at 12:29 PM, John W. Linville <linville@...driver.com> wrote:
> 
> > Cool!  I'm glad we agree.  Now we just need some switch hardware
> > drivers that fit the general model outlined above...
> 
> Why wait?  Let’s create a switch device in qemu and then write the
> model/sample driver to that.  Put a PCI front end on the qemu device
> which is mapped to kernel, and define a register set to represent all
> the switch-like ops we want to offload, in a generic way.  Throw in
> some DMA for CPU-bound I/O (ctrl traffic).  On the qemu device back
> end, expose the ports as taps or whatever so we can wire to real-world
> link partners on the host side.

Not a bad idea at all.  This probably needs further discussion and/or
a spec...and a QEMU hacker.  Where is my friend PJ when I need him? ;-)

> > I would be happy to maintain a kernel.org git tree as a nursery for
> > such drivers as they develop and mature, and I'm sure my daytime
> > employer would be happy to support me on that.  I wonder if we can
> > get any switch people from Intel, Mellanox, Broadcom, or elsewhere
> > to play along?
> 
> My gut tells me this is a build-it-and-they-will-come situation.

No doubt -- in the meantime, feel free to Cc me on some patches!

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