[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE4R7bAFsi0AL2EyTLQRgKLEBO_G4QYXd554uo+tx8OoWnkDuw@mail.gmail.com>
Date: Wed, 19 Aug 2015 22:00:36 -0700
From: Scott Feldman <sfeldma@...il.com>
To: Premkumar Jonnala <pjonnala@...adcom.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] bridge: Enable configuration of ageing interval for
bridges and switch devices.
On Wed, Aug 19, 2015 at 9:56 PM, Premkumar Jonnala
<pjonnala@...adcom.com> wrote:
> Thank you Scott. Please see inline.
>
>> >> -----Original Message-----
>> >> From: Scott Feldman [mailto:sfeldma@...il.com]
>> >> Sent: Tuesday, August 18, 2015 12:48 PM
>> >> To: Premkumar Jonnala
>> >> Cc: netdev@...r.kernel.org
>> >> Subject: Re: [PATCH] bridge: Enable configuration of ageing interval for
>> bridges
>> >> and switch devices.
>> >>
>> >>
>> >>
>> >> On Fri, 14 Aug 2015, Premkumar Jonnala wrote:
>> >>
>> >> > Bridge devices have ageing interval used to age out MAC addresses
>> >> > from FDB. This ageing interval was not configuratble.
>> >> >
>> >> > Enable netlink based configuration of ageing interval for bridges and
>> >> > switch devices. The ageing interval changes the timer used to purge
>> >> > inactive FDB entries in bridges. The ageing interval config is
>> >> > propagated to switch devices, so that platform or hardware based
>> >> > ageing works according to configuration.
>> >> >
>> >> > Signed-off-by: Premkumar Jonnala <pjonnala@...adcom.com>
>> >>
>> >> Hi Premkumar,
>> >>
>> >> I agree with Roopa that we should use existing IFLA_BR_AGEING_TIME.
>> >
>> > What is the motivation for using 'ip link' command to configure bridge
>> attributes? IMHO,
>> > bridge command is better suited for that.
>>
>> Can you extend bridge command to allow setting/getting these bridge
>> attrs? Looks like you construct a RTM_NEWLINK IFLA_INFO_DATA msg. No
>> changes needed to the kernel.
>>
>> bridge link set dev br0 ageing_time 1000
>>
>> --or--
>>
>> ip link set dev br0 type bridge ageing_time 1000
>
> I'd prefer to deprecate/remove all the 6 options on the 'ip link' command and move them to 'bridge' command.
We're probably stuck with the 'ip link' commands, since they're
already release in the wild and folks may have dependency on them.
However, when looking at iproute2 code, look for opportunity to use
same code for both paths.
-scott
--
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