netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Vosburgh <fubar@us.ibm.com>
To: netdev@vger.kernel.org
Cc: Jeff Garzik <jgarzik@pobox.com>
Subject: [PATCH net-next-2.6 0/8] bonding: Fixes and updates
Date: Sat, 17 May 2008 21:10:06 -0700	[thread overview]
Message-ID: <12110838143907-git-send-email-fubar@us.ibm.com> (raw)

	Eight patches for bonding; these apply to net-next-2.6.  This
patch set supersedes the previously posted set of 2 ARP monitor changes
(those are included here).

	1- Convert to msecs_to_jiffies instead of doing math to compute
monitor rearm time.  This is cleaner, and fixes an infinite loop.

	2- Remove test for bonding master having an IP address in the ARP
monitor.  Removing this test permits the ARP monitor to run when bonding
is under some virtual device, such as Xen.  Changes the way some ARP
probes look, but is not a loss of functionality.

	3- Remove redundant argument from bond_create.  It once was used
for something, but now is not.

	4- Relax _safe interations.  Some list interations are fine
without using the _safe versions.

	5- Remove unneeded list_empty checks.  Self explanatory.

	6- Optionally send multiple gratuitous ARPs during failover.  Adds
a configurable parameter to specify the number of grat ARPs to send.
Intended for use with IPoIB.

	7- Refactor ARP monitor for active-backup mode.  Split the current
monolithic function into three: inspection, commit, and probe.  Done
primarily to get RTNL semantics right for next patch.  This could have
been done via conditional locking (as miimon was), but this feels like a
cleaner solution.

	8- Add a "follow" option to fail_over_mac.  This causes the
bonding master to take the MAC of the first slave, but not program the
other slaves with that MAC address.  During failover, the MAC moves to the
new currently active slave.  For multiport devices that can't handle
having all ports set to the same MAC (but still want the benefits of the
bond's MAC not changing during failover).

	Patches are against net-next-2.6.  Please apply.

	Also, I'll be unavailable next week (which is unfortunate timing,
but I didn't want these to wait another week), so if there's discussion
that comes up, I'll answer and revise as needed when I return.

	Thanks,

	-J

---
	-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com

             reply	other threads:[~2008-05-18  4:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-18  4:10 Jay Vosburgh [this message]
     [not found] ` <12110838151824-git-send-email-fubar@us.ibm.com>
2008-05-18  4:10   ` [PATCH 2/8] bonding: remove test for IP in ARP monitor Jay Vosburgh
2008-05-18  4:10     ` [PATCH 3/8] bonding: Remove redundant argument from bond_create Jay Vosburgh
2008-05-18  4:10       ` [PATCH 4/8] bonding: Relax unneeded _safe lists iterations Jay Vosburgh
2008-05-18  4:10         ` [PATCH 5/8] bonding: Remove unneeded list_empty checks Jay Vosburgh
2008-05-18  4:10           ` [PATCH 6/8] bonding: Send more than one gratuitous ARP when slave takes over Jay Vosburgh
2008-05-18  4:10             ` [PATCH 7/8] bonding: refactor ARP active-backup monitor Jay Vosburgh
2008-05-18  4:10               ` [PATCH 8/8] bonding: Add "follow" option to fail_over_mac Jay Vosburgh
2008-05-22 11:09                 ` Jeff Garzik
2008-05-20 21:54             ` [PATCH 6/8] bonding: Send more than one gratuitous ARP when slave takes over Andrew Morton
2008-05-20 21:46       ` [PATCH 3/8] bonding: Remove redundant argument from bond_create Andrew Morton

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=12110838143907-git-send-email-fubar@us.ibm.com \
    --to=fubar@us.ibm.com \
    --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).