[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53334874.8000004@mojatatu.com>
Date: Wed, 26 Mar 2014 17:36:52 -0400
From: Jamal Hadi Salim <jhs@...atatu.com>
To: "John W. Linville" <linville@...driver.com>,
Thomas Graf <tgraf@...g.ch>
CC: Neil Horman <nhorman@...driver.com>, Jiri Pirko <jiri@...nulli.us>,
Florian Fainelli <f.fainelli@...il.com>,
netdev <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>, andy@...yhouse.net,
dborkman@...hat.com, ogerlitz@...lanox.com, jesse@...ira.com,
pshelar@...ira.com, 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>
Subject: Re: [patch net-next RFC 0/4] introduce infrastructure for support
of switch chip datapath
On 03/26/14 11:22, John W. Linville wrote:
> This part makes sense to me -- use the hardware forwarding offloads if
> they are available, but fall back to software for sake of flexibility.
> It gives the admin enough rope to shoot himself in the foot...
>
This should be left up to policy. Maybe a sysctl? Example:
I should be able to choose whether i want to _only_
use the L3 table in hardware and not in software for certain
traffic which may require lower latency.
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