[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140327140309.GD31168@tuxdriver.com>
Date: Thu, 27 Mar 2014 10:03:10 -0400
From: "John W. Linville" <linville@...driver.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Jamal Hadi Salim <jhs@...atatu.com>, Thomas Graf <tgraf@...g.ch>,
netdev@...r.kernel.org, davem@...emloft.net, nhorman@...driver.com,
andy@...yhouse.net, dborkman@...hat.com, ogerlitz@...lanox.com,
jesse@...ira.com, pshelar@...ira.com, azhou@...ira.com,
ben@...adent.org.uk, stephen@...workplumber.org,
jeffrey.t.kirsher@...el.com, vyasevic@...hat.com,
xiyou.wangcong@...il.com, john.r.fastabend@...el.com,
edumazet@...gle.com, sfeldma@...ulusnetworks.com,
f.fainelli@...il.com, roopa@...ulusnetworks.com,
dev@...nvswitch.org
Subject: Re: [patch net-next RFC v2 0/6] introduce infrastructure for support
of switch chip datapath
On Thu, Mar 27, 2014 at 01:57:11PM +0100, Jiri Pirko wrote:
> Thu, Mar 27, 2014 at 01:32:35PM CET, jhs@...atatu.com wrote:
> >On 03/27/14 08:00, Thomas Graf wrote:
> >
> >>It seems like we reached pretty good consensus on the model. What
> >>remaining issues do you see with the port model proposed in v2?
> >>
> >
> >Are we really following the same thread?
> >I dont see any rallying behind Jiri's approach from the
> >other folks who have their own code and way of approaching things.
> >I am hoping we dont continue with the split that is there
> >already.
>
> It is not a split. It is just a completion of a model. Adding missing
> parts. At least I see it that way.
I probably wouldn't call it a 'split' either. But, I agree with
Jamal that we are nowhere near consensus so far.
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
Powered by blists - more mailing lists