[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <533408C0.8000608@mojatatu.com>
Date: Thu, 27 Mar 2014 07:17:20 -0400
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Thomas Graf <tgraf@...g.ch>
CC: Jiri Pirko <jiri@...nulli.us>, 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, linville@...driver.com,
dev@...nvswitch.org
Subject: Re: [patch net-next RFC v2 0/6] introduce infrastructure for support
of switch chip datapath
On 03/27/14 07:02, Thomas Graf wrote:
> On 03/27/14 at 06:27am, Jamal Hadi Salim wrote:
> There is definitely need beyond an ndo that is capable of
> adding flows. You mention routes. Another example would be
> devices capable of offloading iptables & nft rules.
>
nod.
> But wouldn't you want to introduce an additional ndo to
> cover these?
We could - I just find it distracting at the current thread
of discussion (the openwrt folks for example dont need any
or most of that).
> What speaks against going with what Jiri proposes and adjust
> & extend as needed as we go along?
>
I was hoping we knock these issue one at a time. The noise right
now is around ports and stacking of ports etc. Which in my
opinion is an easier topic to handle.
Jiri's patches on this can always come back in the discussion
later.
cheers,
jamal
--
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