From: Florin Malita <fmalita@gmail.com>
To: "Jason R. Martin" <nsxfreddy@gmail.com>
Cc: akpm@osdl.org, davem@davemloft.net,
ctindel@users.sourceforge.net, fubar@us.ibm.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bonding-devel@lists.sourceforge.net
Subject: Re: [PATCH] channel bonding: add support for device-indexed parameters
Date: Thu, 22 Sep 2005 09:16:08 -0400 [thread overview]
Message-ID: <20050922091608.5ec2724c.fmalita@gmail.com> (raw)
In-Reply-To: <c295378405092123032534d93b@mail.gmail.com>
On Wed, 21 Sep 2005 23:03:53 -0700
"Jason R. Martin" <nsxfreddy@gmail.com> wrote:
> Personally I think working to get the sysfs support finished in
> bonding and stop relying on module parameters to configure bonds would
> be better, since bonds will truly be independent of each other and be
> able to be added and removed on the fly. Having worked with a
> previous attempt to set per-bond values through module parameters
> (http://marc.theaimsgroup.com/?t=110558187800001&r=1&w=2), it's easy
> to get pretty crazy.
Agreed - that would be a better configuration interface, but I don't see
why we couldn't support module parameter arrays too. Especially since
the changes are minimal and don't break the ABI/ifenslave
compatibility/etc.
IMHO the "primary" semantics are completely broken right now and this
is a possible fix for it.
> For example, you can have more than one
> arp_ip_target, and they really should be per bond as well, so how do
> you divvy those up via module parameters?
Yup, arp_ip_target is one parameter which doesn't lend itself to this
scheme and this is exactly why the patch doesn't try to fix it.
Florin
next prev parent reply other threads:[~2005-09-22 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 4:04 [PATCH] channel bonding: add support for device-indexed parameters Florin Malita
2005-09-22 6:03 ` Jason R. Martin
2005-09-22 13:16 ` Florin Malita [this message]
2005-09-26 23:58 ` Jay Vosburgh
2005-09-27 5:24 ` Florin Malita
2005-09-27 7:11 ` Jay Vosburgh
2005-09-27 13:40 ` Florin Malita
2005-09-27 13:54 ` [Bonding-devel] " Eric Paris
2005-09-27 14:10 ` Florin Malita
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=20050922091608.5ec2724c.fmalita@gmail.com \
--to=fmalita@gmail.com \
--cc=akpm@osdl.org \
--cc=bonding-devel@lists.sourceforge.net \
--cc=ctindel@users.sourceforge.net \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsxfreddy@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).