From: jamal <hadi@cyberus.ca>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net
Subject: Re: [RFC/PATCH][Bonding]: keep slave state when admin down
Date: Thu, 03 Aug 2006 08:25:26 -0400 [thread overview]
Message-ID: <1154607926.5205.8.camel@jzny2> (raw)
In-Reply-To: <1153426931.5273.136.camel@jzny2>
Jay,
I have tested with a standard bootup script - which amongst other things
brings down the bond and gives it a new MAC before bringing it up.
What do you wanna do with the patch? I know if it sits with me it will
be lost.
cheers,
jamal
On Thu, 2006-20-07 at 16:22 -0400, jamal wrote:
> On Thu, 2006-20-07 at 11:50 -0700, Jay Vosburgh wrote:
>
> >
> > Do the initscript and sysconfig packages (/sbin/ifup, ifdown,
> > that stuff in /etc/sysconfig/network-scripts, etc) do the right thing
> > with this change?
> >
>
> I havent seen issues so far.
>
> > If memory serves, the initscripts will down the bond during
> > setup; I'm not sure if there is any dependency on that action releasing
> > all (possibly preexisting) slaves.
> >
>
> The one i have experimented with has no issues - but you may be right
> some people depend on this behavior at shutdown.
>
> > I don't have a big problem with this, but I'm a little concerned
> > that there may be dependencies on the existing behavior.
>
> I could add a module parameter that restores old behavior when asked to
> and we keep that for a while and have it print a warning message.
> The other alternative is just release it and see if someone complains.
>
> cheers,
> jamal
prev parent reply other threads:[~2006-08-03 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 13:19 [RFC/PATCH][Bonding]: keep slave state when admin down jamal
2006-07-20 18:50 ` Jay Vosburgh
2006-07-20 20:22 ` jamal
2006-08-03 12:25 ` jamal [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=1154607926.5205.8.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.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