netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <nikolay@redhat.com>
To: Mahesh Bandewar <maheshb@google.com>,
	Jay Vosburgh <j.vosburgh@gmail.com>,
	Andy Gospodarek <andy@greyhouse.net>,
	Veaceslav Falico <vfalico@gmail.com>,
	David Miller <davem@davemloft.net>
Cc: Maciej Zenczykowski <maze@google.com>,
	netdev <netdev@vger.kernel.org>,
	Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH next v4 4/6] bonding: Allow userspace to set actors' system_priority in AD system
Date: Wed, 18 Feb 2015 13:50:35 +0100	[thread overview]
Message-ID: <54E48A9B.3020409@redhat.com> (raw)
In-Reply-To: <1424243874-27109-1-git-send-email-maheshb@google.com>

On 02/18/2015 08:17 AM, Mahesh Bandewar wrote:
> This patch allows user to randomize the system-priority in an ad-system.
> The allowed range is 1 - 0xFFFF while default value is 0xFFFF. If user
> does not specify this value, the system defaults to 0xFFFF, which is
> what it was before this patch.
> 
> Following example code could set the value -
>     # modprobe bonding mode=4
>     # sys_prio=$(( 1 + RANDOM + RANDOM ))
>     # echo $sys_prio > /sys/class/net/bond0/bonding/ad_actor_sys_prio
>     # echo +eth1 > /sys/class/net/bond0/bonding/slaves
>     ...
>     # ip link set bond0 up
> 
> Signed-off-by: Mahesh Bandewar <maheshb@google.com>
> ---
> v1:
>   Initial version
> v2:
>   Rename ad_actor_system_priority to ad_actor_sys_prio
> v3-v4:
>   Rebase
> 
>  Documentation/networking/bonding.txt |  9 +++++++++
>  drivers/net/bonding/bond_3ad.c       |  5 ++++-
>  drivers/net/bonding/bond_main.c      | 14 ++++++++++++++
>  drivers/net/bonding/bond_options.c   | 29 ++++++++++++++++++++++++++++-
>  drivers/net/bonding/bond_procfs.c    |  2 ++
>  drivers/net/bonding/bond_sysfs.c     | 15 +++++++++++++++
>  include/net/bond_options.h           |  1 +
>  include/net/bonding.h                |  1 +
>  8 files changed, 74 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/networking/bonding.txt b/Documentation/networking/bonding.txt
> index 83bf4986baea..f19d888651b8 100644
> --- a/Documentation/networking/bonding.txt
> +++ b/Documentation/networking/bonding.txt
> @@ -178,6 +178,15 @@ active_slave
>  	active slave, or the empty string if there is no active slave or
>  	the current mode does not use an active slave.
>  
> +ad_actor_sys_prio
> +
> +	In an AD system, this specifies the system priority. The allowed range
> +	is 1 - 65535. If the value is not specified, it takes 65535 as the
> +	default value.
> +
> +	This paramter has effect only in 802.3ad mode and is available through
^^^^^^^^^^^^^^^^^^^^^
s/paramter/parameter/

> +	SysFs interface.
> +

      reply	other threads:[~2015-02-18 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18  7:17 [PATCH next v4 4/6] bonding: Allow userspace to set actors' system_priority in AD system Mahesh Bandewar
2015-02-18 12:50 ` Nikolay Aleksandrov [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=54E48A9B.3020409@redhat.com \
    --to=nikolay@redhat.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=j.vosburgh@gmail.com \
    --cc=maheshb@google.com \
    --cc=maze@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=vfalico@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;
as well as URLs for NNTP newsgroup(s).