From: Stephen Hemminger <stephen@networkplumber.org>
To: Vincent Bernat <vincent@bernat.ch>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] ip: bond: add peer notification delay support
Date: Sun, 7 Jul 2019 11:40:41 -0700 [thread overview]
Message-ID: <20190707114041.4f068bee@xps13.lan> (raw)
In-Reply-To: <20190707175115.3704-1-vincent@bernat.ch>
On Sun, 7 Jul 2019 19:51:15 +0200
Vincent Bernat <vincent@bernat.ch> wrote:
> Ability to tweak the delay between gratuitous ND/ARP packets has been
> added in kernel commit 07a4ddec3ce9 ("bonding: add an option to
> specify a delay between peer notifications"), through
> IFLA_BOND_PEER_NOTIF_DELAY attribute. Add support to set and show this
> value.
>
> Example:
>
> $ ip -d link set bond0 type bond peer_notify_delay 1000
> $ ip -d link l dev bond0
> 2: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue
> state UP mode DEFAULT group default qlen 1000
> link/ether 50:54:33:00:00:01 brd ff:ff:ff:ff:ff:ff
> bond mode active-backup active_slave eth0 miimon 100 updelay 0
> downdelay 0 peer_notify_delay 1000 use_carrier 1 arp_interval 0
> arp_validate none arp_all_targets any primary eth0
> primary_reselect always fail_over_mac active xmit_hash_policy
> layer2 resend_igmp 1 num_grat_arp 5 all_slaves_active 0 min_links
> 0 lp_interval 1 packets_per_slave 1 lacp_rate slow ad_select
> stable tlb_dynamic_lb 1 addrgenmode eu
>
> Signed-off-by: Vincent Bernat <vincent@bernat.ch>
Looks good. I notice that all these flags don't show up in any man page.
Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2019-07-07 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 21:11 [PATCH iproute2-next] ip: bond: add peer notification delay support Vincent Bernat
2019-07-07 16:41 ` Stephen Hemminger
2019-07-07 17:51 ` Vincent Bernat
2019-07-07 18:40 ` Stephen Hemminger [this message]
2019-07-07 20:06 ` Vincent Bernat
2019-07-10 20:54 ` David Ahern
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=20190707114041.4f068bee@xps13.lan \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=vincent@bernat.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.