From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Dan Williams <dcbw@redhat.com>
Cc: David Miller <davem@davemloft.net>,
james@nurealm.net, futur.andy@googlemail.com,
kvalo@codeaurora.org, arend.vanspriel@broadcom.com,
maheshb@google.com, andy@greyhouse.net, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, greearb@candelatech.com
Subject: Re: Regression: Bug 196547 - Since 4.12 - bonding module not working with wireless drivers
Date: Wed, 16 Aug 2017 22:33:41 -0700 [thread overview]
Message-ID: <28296.1502948021@famine> (raw)
In-Reply-To: <1502935907.30484.4.camel@redhat.com>
Dan Williams <dcbw@redhat.com> wrote:
[...]
>You'll probably say "aim for the 75% case" or something like that,
>which is fine, but then you're depending on your 75% case to be (a)
>single AP, (b) never move (eg, only bond wifi + ethernet), (c) little
>radio interference. I'm not sure I'd buy that. If I've put words in
>your mouth, forgive me.
The primary use case that I'm aware of for bonding with wireless
devices is in active-backup mode, paired with an ethernet adapter set as
the bonding "primary" device. I think this is the case that absolutely
should just work. I don't think bonding cares (or should care) about
(a) - (c) for this use.
Your point (b) suggests that there are use cases other than the
above; I'm unfamiliar with any use other than wifi + ethernet, can you
elaborate?
-J
---
-Jay Vosburgh, jay.vosburgh@canonical.com
prev parent reply other threads:[~2017-08-17 5:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 5:39 Regression: Bug 196547 - Since 4.12 - bonding module not working with wireless drivers Kalle Valo
2017-08-10 12:43 ` Arend van Spriel
2017-08-10 17:52 ` Andreas Born
2017-08-11 13:14 ` Kalle Valo
2017-08-12 7:35 ` Kalle Valo
2017-08-12 19:30 ` James Feeney
2017-08-13 17:42 ` Andreas Born
2017-08-16 20:44 ` James Feeney
2017-08-16 21:01 ` David Miller
2017-08-16 21:22 ` Dan Williams
2017-08-16 21:31 ` David Miller
2017-08-17 2:11 ` Dan Williams
2017-08-17 2:36 ` Ben Greear
2017-08-17 3:18 ` Dan Williams
2017-08-17 3:32 ` Ben Greear
2017-08-17 2:42 ` David Miller
2017-08-17 5:33 ` Jay Vosburgh [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=28296.1502948021@famine \
--to=jay.vosburgh@canonical.com \
--cc=andy@greyhouse.net \
--cc=arend.vanspriel@broadcom.com \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=futur.andy@googlemail.com \
--cc=greearb@candelatech.com \
--cc=james@nurealm.net \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maheshb@google.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).