[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5460E3D5.3000104@cumulusnetworks.com>
Date: Mon, 10 Nov 2014 08:12:05 -0800
From: Roopa Prabhu <roopa@...ulusnetworks.com>
To: Jamal Hadi Salim <jhs@...atatu.com>
CC: Scott Feldman <sfeldma@...il.com>, Jiri Pirko <jiri@...nulli.us>,
Netdev <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>, nhorman@...driver.com,
Andy Gospodarek <andy@...yhouse.net>,
Thomas Graf <tgraf@...g.ch>, dborkman@...hat.com,
ogerlitz@...lanox.com, jesse@...ira.com, pshelar@...ira.com,
azhou@...ira.com, ben@...adent.org.uk, stephen@...workplumber.org,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
vyasevic@...hat.com, xiyou.wangcong@...il.com,
"Fastabend, John R" <john.r.fastabend@...el.com>,
edumazet@...gle.com, Florian Fainelli <f.fainelli@...il.com>,
John Linville <linville@...driver.com>, jasowang@...hat.com,
ebiederm@...ssion.com, nicolas.dichtel@...nd.com,
ryazanov.s.a@...il.com, buytenh@...tstofly.org,
aviadr@...lanox.com, nbd@...nwrt.org, alexei.starovoitov@...il.com,
Neil.Jerram@...aswitch.com, ronye@...lanox.com,
simon.horman@...ronome.com, alexander.h.duyck@...hat.com,
"Ronciak, John" <john.ronciak@...el.com>, mleitner@...hat.com,
Shrijeet Mukherjee <shrijeet@...il.com>,
Andy Gospodarek <gospo@...ulusnetworks.com>,
Benjamin LaHaise <bcrl@...ck.org>
Subject: Re: [patch net-next v2 10/10] rocker: implement L2 bridge offloading
On 11/10/14, 4:27 AM, Jamal Hadi Salim wrote:
> On 11/10/14 03:46, Scott Feldman wrote:
>
>>
>> IFLA_BRPORT_LEARNING is u8 attr and we're only using lower bit to turn
>> learning on/off. Maybe we can use another bit to indicate learning to
>> be done in sw or hw. I don't think adding another bit would break
>> existing iproute2.
>>
>> LEARNING_ENABLED (1 << 0)
>> LEARNING_HW (1 << 1)
>>
>> Would this work?
>>
>
> Yes to making it a bit. But:
> This is not *learning*. You are doing a *sync*.
> Those are two different things.
>
> Learning on/off exists today. It signals to the L2 whether you
> should learn or not.
> I like the way fdb_add/del work with a flag which says
> it is the software and/or offloaded version. Please keep that
> semantic.
> What you are doing above is letting the hardware learn then
> syncing to software. You need a different flag there. something
> like:
>
> SYNC_HW_FDB (1<<1)
>
And in any case, It seems like this policy should be per bridge or per
switch chip...or per fdb..
entry (like the original fdb_add/del) and not a "port" flag.. ?
--
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