From: Patrick Simmons <linuxrocks123@netscape.net>
To: netdev@vger.kernel.org, Jay Vosburgh <j.vosburgh@gmail.com>,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <gospo@cumulusnetworks.com>
Subject: Re: [PATCH] Experimental new bonding driver mode=batman
Date: Tue, 19 May 2015 04:29:45 -0400 [thread overview]
Message-ID: <555AF479.7000603@netscape.net> (raw)
In-Reply-To: <20150519074941.GB17391@unicorn.suse.cz>
On 05/19/2015 03:49 AM, Michal Kubecek wrote:
> On Tue, May 19, 2015 at 02:09:43AM -0400, Patrick Simmons wrote:
>>
>> I've written a new mode for the kernel bonding driver. It's similar to
>> the round-robin mode, but it keeps statistics on TCP resends so as to
>> favor slave devices with more bandwidth when choosing where to send
>> packets. I've tested it on two laptops using WiFi/Ethernet and it seems
>> to work okay, but it should be considered experimental.
>
> A description of how is the mode supposed to work would be definitely
> helpful.
>
Rationale: It's helpful for cases where the slave devices have
significantly different or varying bandwidth. The reason I wrote it is
to bond powerline networking and wireless networking adapters into a
single interface for use with connecting to a MythTV server. Neither of
these systems is particularly reliable with bandwidth, but mode=batman
can adaptively figure out which network has more available bandwidth at
any given moment. This is better than mode=round-robin which always
balances everything 50/50.
Regarding your analysis, I appreciate your comments, and I know it's
rough, but I'm sorry to say I'm not really interested in doing much to
improve its polish past where it is. If it fails some way when I try to
deploy it, then I'll fix that, and maybe I'll play around with the
balancing heuristics, but the code quality is what it is unless someone
else wants to improve it. I would fix the indentation if that would
make it acceptable for you to merge it, but not much more. My argument
for merging it is basically "it doesn't do anything unless you pass
mode=batman, so what's the harm?".
So, if you guys decide you don't want to merge it because of the global
spinlock etc., that's cool and I understand, but I thought I should at
least post to this list so you and any other potentially interested
people know it exists. Oh, and, if you're not going to merge it, please
let me know so I can know post the patch to GitHub or somewhere. And,
if you could include a note in the comments at the top of bond_main.c or
somewhere pointing people to the patch, I'd very much appreciate that.
I don't want anyone else to have to endure hours of kernel rebuilds with
KASAN enabled if they want this functionality :)
Cheers and have a good one!
--Patrick
--
If I'm not here, I've gone out to find myself. If I get back before I
return, please keep me here.
next prev parent reply other threads:[~2015-05-19 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 6:09 [PATCH] Experimental new bonding driver mode=batman Patrick Simmons
2015-05-19 7:49 ` Michal Kubecek
2015-05-19 8:29 ` Patrick Simmons [this message]
2015-05-20 7:32 ` Michal Kubecek
2015-05-20 17:45 ` Jay Vosburgh
2015-05-20 20:04 ` Andy Gospodarek
2015-05-20 22:48 ` Patrick Simmons
2015-05-20 22:37 ` Patrick Simmons
2015-05-19 7:58 ` Jonathan Toppins
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=555AF479.7000603@netscape.net \
--to=linuxrocks123@netscape.net \
--cc=gospo@cumulusnetworks.com \
--cc=j.vosburgh@gmail.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).