From: Jay Vosburgh <fubar@us.ibm.com>
To: netdev@vger.kernel.org
Cc: Jeff Garzik <jgarzik@pobox.com>, David Miller <davem@davemloft.net>
Subject: [PATCH net-next-2.6 0/5] bonding: Fixes and updates
Date: Fri, 13 Jun 2008 18:11:59 -0700 [thread overview]
Message-ID: <12134059242107-git-send-email-fubar@us.ibm.com> (raw)
Five patches for bonding; these apply to net-next-2.6.
Patches 1 - 3 comprise support for NETDEV_BONDING_FAILOVER
notifiers; the first patch adds the define, the second cleans up part of
bonding in preparation for the notifier call, and the third adds the
notifier call itself.
Patch 4 cleans up and improves previously added support for
specifying the number of gratuitous ARPs to be issued at failover time for
the active-backup mode.
Patch 5 permits specifying max_bonds as zero (creating no bond0
device). Also provides an API from net/core to create and destroy files
in net_class so that /sys/class/net/bonding_masters will be created. This
was previously done by backtracking from the first bonding device's sysfs
information (dev->dev.class).
Please apply.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next reply other threads:[~2008-06-14 1:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 1:11 Jay Vosburgh [this message]
2008-06-14 1:12 ` [PATCH 1/5] net/core: add NETDEV_BONDING_FAILOVER event Jay Vosburgh
2008-06-14 1:12 ` [PATCH 2/5] bonding: bond_change_active_slave() cleanup under active-backup Jay Vosburgh
2008-06-14 1:12 ` [PATCH 3/5] bonding: deliver netdev event for fail-over under the active-backup mode Jay Vosburgh
2008-06-14 1:12 ` [PATCH 4/5] bonding: Rework / fix multiple gratuitous ARP support Jay Vosburgh
2008-06-14 1:12 ` [PATCH 5/5] bonding: Allow setting max_bonds to zero Jay Vosburgh
2008-06-18 3:31 ` Jeff Garzik
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=12134059242107-git-send-email-fubar@us.ibm.com \
--to=fubar@us.ibm.com \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.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;
as well as URLs for NNTP newsgroup(s).