From: "Or Gerlitz" <ogerlitz@voltaire.com>
To: "Jay Vosburgh" <fubar@us.ibm.com>
Cc: netdev@vger.kernel.org, "Roland Dreier" <rdreier@cisco.com>,
openib-general@openib.org
Subject: Re: [RFC] [PATCH V2 0/3] bonding support for operation over IPoIB
Date: Thu, 11 Jan 2007 17:03:13 +0200 [thread overview]
Message-ID: <45A651B1.9090402@voltaire.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611301256130.26156@zuben>
Or Gerlitz wrote:
> This patch series is a second version (see below link to V1) of the suggested
> changes to the bonding driver such that it would be able to support non ARPHRD_ETHER
> netdevices for its High-Availability (active-backup) mode.
>
> The motivation is to enable the bonding driver on its HA mode to work with the
> IP over Infiniband (IPoIB) driver. With these patches I was able to enslave
> IPoIB netdevices and run TCP, UDP, IP (UDP) Multicast and ICMP traffic with
> fail-over and fail-back working fine. My working env was the net-2.6.20 git.
> These patches are not enough for configuration of IPoIB bonding through tools
> (eg /sbin/ifenslave and /sbin/ifup) provided by packages such as sysconfig and
> initscripts, specifically since these tools sets the bonding device to be UP
> before enslaving anything. Once this patchset gets positive/feedback the next step
> would be to look how to enhance the tools/packages so it would be possible to
> bond/enslave with the modified code. As suggested by the bonding maintainer, this
> step can potentially involve converting ifenslave to be a script based on the bonding
> sysfs infrastructure rather on the somehow obsoleted Documentation/networking/ifenslave.c
Jay,
I would like to move forward and push the V2 patch series upstream
through netdev and then start working on the configuration tools etc
changes needed to support bonding IPoIB devices through non direct
bonding sysfs scripts... are you OK with that?
If you agree to the push, who is doing this nowadays, is it Jeff Garzik
or David Miller?
Roland - any other comments/concerns that you might have are very much
appreciated.
Or.
prev parent reply other threads:[~2007-01-11 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 10:56 [RFC] [PATCH V2 0/3] bonding support for operation over IPoIB Or Gerlitz
2006-11-30 10:57 ` [RFC][PATCH V2 1/3] enable bonding to enslave non ARPHRD_ETHER netdevices Or Gerlitz
2006-11-30 11:09 ` Or Gerlitz
2006-11-30 10:57 ` [RFC][PATCH V2 2/3] enable bonding to enslave netdevices not supporting set_mac_address() Or Gerlitz
2006-11-30 10:58 ` [RFC] [PATCH V2 3/3] enable IP multicast for bonding IPoIB devices - allow not UP enslavement Or Gerlitz
2006-11-30 11:00 ` [RFC] [PATCH V2 0/3] bonding support for operation over IPoIB - example config script Or Gerlitz
2007-01-11 15:03 ` Or Gerlitz [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=45A651B1.9090402@voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.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).