public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Flavio Leitner <fbl@sysclose.org>
Cc: netdev <netdev@vger.kernel.org>, Scott Feldman <sfeldma@gmail.com>
Subject: Re: Cannot set ageing to zero
Date: Tue, 26 Jan 2016 18:48:30 +0100	[thread overview]
Message-ID: <20160126174830.GE2195@nanopsycho.orion> (raw)
In-Reply-To: <20160126154424.68185099@x240.home>

Tue, Jan 26, 2016 at 06:44:24PM CET, fbl@sysclose.org wrote:
>On Tue, 26 Jan 2016 18:30:41 +0100
>Jiri Pirko <jiri@resnulli.us> wrote:
>
>> Tue, Jan 26, 2016 at 06:26:30PM CET, fbl@sysclose.org wrote:
>> >
>> >Hi,
>> >
>> >After the commit[1] below, we can't set ageing on a Linux bridge
>> >device to zero.  It seems rocker needs the minimum value, but we
>> >can't break an old and valid Linux bridge behavior.   
>> 
>> The commit below adds check if the value being set is within
>> BR_MIN_AGEING_TIME and BR_MAX_AGEING_TIME. I believe that the check is
>> correct as it implements the standard.
>>
>> Why do you set ageing_time to 0? Why don't just just disable learning?
>
>It's a documented behavior:
>http://www.linuxcertif.com/man/5/ifcfg-bridge/
>http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge
>http://comments.gmane.org/gmane.linux.network.bridge/2060

0 makes entries permanent. Fair enough. Feel free to send patch moving
the check inside switchdev_port_attr_set or into drivers. I can put it
in my todo list if you want.

Thanks!


>
>fbl
>
>> 
>> 
>> >
>> >[1] commit c62987bbd8a1a1664f99e89e3959339350a6131e
>> >Author: Scott Feldman <sfeldma@gmail.com>
>> >Date:   Thu Oct 8 19:23:19 2015 -0700
>> >
>> >    bridge: push bridge setting ageing_time down to switchdev
>> >    
>> >    Use SWITCHDEV_F_SKIP_EOPNOTSUPP to skip over ports in bridge that
>> >    don't support setting ageing_time (or setting bridge attrs in
>> >    general). 
>> >    If push fails, don't update ageing_time in bridge and return err
>> > to user. 
>> >    If push succeeds, update ageing_time in bridge and run gc_timer
>> > now to recalabrate when to run gc_timer next, based on new
>> > ageing_time. 
>> >    Signed-off-by: Scott Feldman <sfeldma@gmail.com>
>> >    Signed-off-by: Jiri Pirko <jiri@resnulli.us>
>> >    Acked-by: Jiri Pirko <jiri@mellanox.com>
>> >    Signed-off-by: David S. Miller <davem@davemloft.net>
>> >
>> >
>> >-- 
>> >fbl
>> >  
>
>
>
>-- 
>fbl
>

      reply	other threads:[~2016-01-26 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 17:26 Cannot set ageing to zero Flavio Leitner
2016-01-26 17:30 ` Jiri Pirko
2016-01-26 17:44   ` Flavio Leitner
2016-01-26 17:48     ` Jiri Pirko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160126174830.GE2195@nanopsycho.orion \
    --to=jiri@resnulli.us \
    --cc=fbl@sysclose.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfeldma@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox