netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason R. Martin" <nsxfreddy@gmail.com>
To: Florin Malita <fmalita@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: Wed, 21 Sep 2005 23:03:53 -0700	[thread overview]
Message-ID: <c295378405092123032534d93b@mail.gmail.com> (raw)
In-Reply-To: <20050922000444.369c32c2.fmalita@gmail.com>

On 9/21/05, Florin Malita <fmalita@gmail.com> wrote:
> While originally I was interested in being able to set a different
> primary interface for each bond device (same primary for all bond
> devices doesn't make any sense), most parameters deserve the same
> treatement.
>
> This patch adds support for device indexed module parameter
> arrays instead of the old plain scalars. Mostly module_param
> substitutions and parameter parsing logic tweaking.
[snip]

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.  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?

Jason

  reply	other threads:[~2005-09-22  6:03 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 [this message]
2005-09-22 13:16   ` Florin Malita
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=c295378405092123032534d93b@mail.gmail.com \
    --to=nsxfreddy@gmail.com \
    --cc=akpm@osdl.org \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=ctindel@users.sourceforge.net \
    --cc=davem@davemloft.net \
    --cc=fmalita@gmail.com \
    --cc=fubar@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).