From: Andrew Lunn <andrew@lunn.ch>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: Roopa Prabhu <roopa@cumulusnetworks.com>,
bridge@lists.linux-foundation.org,
netdev <netdev@vger.kernel.org>
Subject: Validation of forward_delay seems wrong...
Date: Tue, 2 Jul 2019 22:47:05 +0200 [thread overview]
Message-ID: <20190702204705.GC28471@lunn.ch> (raw)
Hi Nikolay
The man page says that the bridge forward_delay is in units of
seconds, and should be between 2 and 30.
I've tested on a couple of different kernel versions, and this appears
to be not working correctly:
ip link set br0 type bridge forward_delay 2
RTNETLINK answers: Numerical result out of range
ip link set br0 type bridge forward_delay 199
RTNETLINK answers: Numerical result out of range
ip link set br0 type bridge forward_delay 200
#
ip link set br0 type bridge forward_delay 3000
#
ip link set br0 type bridge forward_delay 3001
RTNETLINK answers: Numerical result out of range
I've not checked what delay is actually being used here, but clearly
something is mixed up.
grep HZ .config
CONFIG_HZ_PERIODIC=y
# CONFIG_NO_HZ_IDLE is not set
# CONFIG_NO_HZ_FULL is not set
# CONFIG_NO_HZ is not set
CONFIG_HZ_FIXED=0
CONFIG_HZ_100=y
# CONFIG_HZ_200 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_500 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
Thanks
Andrew
next reply other threads:[~2019-07-03 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 20:47 Andrew Lunn [this message]
2019-07-02 21:19 ` Validation of forward_delay seems wrong Nikolay Aleksandrov
2019-07-02 21:21 ` Nikolay Aleksandrov
2019-07-02 21:35 ` Andrew Lunn
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=20190702204705.GC28471@lunn.ch \
--to=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.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