netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nicolas de Pesloüan" <nicolas.2p.debian@gmail.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
	Andy Gospodarek <andy@greyhouse.net>,
	netdev@vger.kernel.org
Subject: Re: bonding and ifenslave version.
Date: Thu, 04 Aug 2011 07:31:38 +0200	[thread overview]
Message-ID: <4E3A2EBA.4040003@gmail.com> (raw)
In-Reply-To: <20110803143338.03988aab@nehalam.ftrdhcpuser.net>

Le 03/08/2011 23:33, Stephen Hemminger a écrit :
> On Wed, 03 Aug 2011 22:38:03 +0200
> Nicolas de Pesloüan<nicolas.2p.debian@gmail.com>  wrote:
<snip>
>> At least, we can:
>> - update the bonding documentation to clarify that ifenslave is deprecated (and move most ifenslave
>> related stuffs at the end of the documentation);
>> - possibly issue a warning when the API is used, suggesting to use sysfs instead.
>>
>> I can take care of the documentation update if appropriate.
>>
>> 	Nicolas.
>
> Or I could just put a shell script that does the same thing in iproute.

You mean, to replace ifenslave (from ifenslave.c) by a shell script by the same name that gives 
users the same command-line interface but use sysfs instead of the ioctl API internally?

I had this in mind two years ago, in a private conversation while changing the ifenslave package on 
Debian.

But chance exist that those who expect ifenslave to work would like to disable sysfs support if not 
used. I assume that totally disabling sysfs at compile time would reduce the size of the kernel far 
more that disabling the ioctl API. So, for those doing embedded things, this may makes sens to have 
an ifenslave version that doesn't rely on sysfs.

Or do you mean, to replace ifenslave (.c) by a shell script that use netlink internally? Are all the 
bonding options available through netlink? I remember many conversation about using netlink for 
bonding setup, but don't remember seeing that in the actual code.

	Nicolas.

  reply	other threads:[~2011-08-04  5:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02 20:06 [PATCH] bonding: document two undocumented options Nicolas de Pesloüan
2011-08-03  6:43 ` bonding and ifenslave version Nicolas de Pesloüan
2011-08-03 19:03   ` Andy Gospodarek
2011-08-03 19:38     ` Nicolas de Pesloüan
2011-08-03 20:07       ` Jay Vosburgh
2011-08-03 20:38         ` Nicolas de Pesloüan
2011-08-03 21:33           ` Stephen Hemminger
2011-08-04  5:31             ` Nicolas de Pesloüan [this message]
2011-08-04 16:57               ` Stephen Hemminger
2011-08-04 21:20                 ` Nicolas de Pesloüan
2011-08-03 10:44 ` [PATCH] bonding: document two undocumented options David Miller
2011-08-03 20:01   ` Nicolas de Pesloüan
2011-08-03 20:59     ` Jay Vosburgh
2011-08-04  5:41       ` Nicolas de Pesloüan
2011-08-06 17:06       ` [PATCH v3] " Nicolas de Pesloüan
2011-08-08  5:16         ` David Miller
2011-08-03 20:02   ` [PATCH] " Nicolas de Pesloüan

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=4E3A2EBA.4040003@gmail.com \
    --to=nicolas.2p.debian@gmail.com \
    --cc=andy@greyhouse.net \
    --cc=fubar@us.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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).