From: "Bjørn Mork" <bjorn@mork.no>
To: David Miller <davem@davemloft.net>
Cc: lkundrak@v3.sk, jay.vosburgh@canonical.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
vfalico@gmail.com, gospo@cumulusnetworks.com
Subject: Re: [PATCH 3/3] bonding: make device count build-time configurable
Date: Tue, 12 Jan 2016 22:40:35 +0100 [thread overview]
Message-ID: <87bn8qv5m4.fsf@nemi.mork.no> (raw)
In-Reply-To: <20160112.154914.397367508465928770.davem@davemloft.net> (David Miller's message of "Tue, 12 Jan 2016 15:49:14 -0500 (EST)")
David Miller <davem@davemloft.net> writes:
> From: Lubomir Rintel <lkundrak@v3.sk>
> Date: Tue, 12 Jan 2016 18:19:49 +0100
>
>> It's still an improvement to let the distributions decide if they're
>> keeping "ip link add" broken or possibly affecting the scripts.
>
> That it is "broken" is your opinion.
>
> Document the behavior. It is not broken if the user is told to be
> mindful of what devices are created by default.
>
> There is way too much downside to changing this.
Besides, distributions or admins can already change that behaviour if
they consider it "broken", using the existing module parameter:
# echo "options bonding max_bonds=0" >/etc/modprobe.d/bonding.conf
# rmmod bonding
# ip link add bond0 type bond
(no error here)
This method should be well known and understood by most users, contrary
to some odd CONFIG_ build time setting.
Bjørn
next prev parent reply other threads:[~2016-01-12 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 11:58 [PATCH 3/3] bonding: make device count build-time configurable Lubomir Rintel
2016-01-12 16:34 ` Jay Vosburgh
2016-01-12 17:19 ` Lubomir Rintel
2016-01-12 19:36 ` Jay Vosburgh
2016-01-12 20:49 ` David Miller
2016-01-12 21:40 ` Bjørn Mork [this message]
2016-02-05 15:07 ` Lubomir Rintel
2016-01-12 20:45 ` David Miller
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=87bn8qv5m4.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=gospo@cumulusnetworks.com \
--cc=jay.vosburgh@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--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