From: Dawid Ciezarkiewicz <dpc@asn.pl>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] wrr (weighted round-robin) bonding
Date: Mon, 16 Oct 2006 21:07:57 +0200 [thread overview]
Message-ID: <200610162107.57477.dpc@asn.pl> (raw)
In-Reply-To: <200610161850.k9GIogZt028527@death.nxdomain.ibm.com>
On Monday, 16 October 2006 20:50, you wrote:
>
> Dawid Ciezarkiewicz <dpc@asn.pl> wrote:
> [...]
> >+ weighted-rr or 7
> >+
> >+ Weighted round-robin bonding. In this mode bonding
> >+ interface will use weights assigned to it's slaves.
> >+
> >+ Each slave can have weight assigned via ioctl (ifenslave).
> >+ These values will be used at the start of each "cycle".
> >+ Each slave will have token counter restored to it's weight.
> >+ Then using round-robin mechanism those tokens are "used"
> >+ to pay for emitted frames. When all token counters are
> >+ zeroed - new "cycle" begins.
>
> Before getting into the technical bits of the patch, what's the
> reason for wanting to do this, and why is this rather complex manual
> weight assignment better than an automatic system based on, e.g., link
> speed of the slaves?
In short:
It was designed as a solution for wireless links bonding - where link quality
can change rather quickly in time. By using wrr bonding, userspace tools can
measure current bandwidth and change bonding slave weights in realtime.
It was written for Lintrack, and you can read about it's usage here:
http://lintrack.org/index.php/about/advantage
next prev parent reply other threads:[~2006-10-16 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 18:21 [RFC] wrr (weighted round-robin) bonding Dawid Ciezarkiewicz
2006-10-16 18:27 ` Dawid Ciezarkiewicz
2006-10-16 18:50 ` Jay Vosburgh
2006-10-16 19:07 ` Dawid Ciezarkiewicz [this message]
2006-10-16 21:30 ` Andy Gospodarek
2006-10-17 8:16 ` Dawid Ciezarkiewicz
2006-10-19 19:04 ` Andy Gospodarek
2006-10-20 19:41 ` Dawid Ciezarkiewicz
2006-10-20 19:53 ` Jay Vosburgh
2006-10-20 20:52 ` Dawid Ciezarkiewicz
2006-10-20 21:35 ` Andy Gospodarek
2006-10-20 21:55 ` Jay Vosburgh
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=200610162107.57477.dpc@asn.pl \
--to=dpc@asn.pl \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
/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).