From: Jeff Garzik <jgarzik@pobox.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [PATCH 1/5] bonding: refactor mii monitor
Date: Thu, 07 Aug 2008 04:00:17 -0400 [thread overview]
Message-ID: <489AAB91.2000202@pobox.com> (raw)
In-Reply-To: <12150481241992-git-send-email-fubar@us.ibm.com>
Jay Vosburgh wrote:
> Refactor mii monitor. As with the previous ARP monitor refactor,
> the motivation for this is to handle locking rationally (in this case,
> removing conditional locking) and generally clean up the code.
>
> This patch breaks up the monolithic mii monitor into two phases:
> an inspection phase, followed by an optional commit phase. The commit phase
> is the only portion that requires RTNL or makes changes to state, and is
> only called when inspection finds something to change.
>
> Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
> ---
> drivers/net/bonding/bond_3ad.c | 1 +
> drivers/net/bonding/bond_main.c | 394 +++++++++++++++++----------------------
> 2 files changed, 173 insertions(+), 222 deletions(-)
applied 1-5
next prev parent reply other threads:[~2008-08-07 8:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 1:21 [PATCH net-next-2.6 0/5] bonding: Refactor, fix, and updates Jay Vosburgh
2008-07-03 1:21 ` [PATCH 1/5] bonding: refactor mii monitor Jay Vosburgh
2008-07-03 1:21 ` [PATCH 2/5] bonding: Don't destroy bonding master when removing slave via sysfs Jay Vosburgh
2008-07-03 1:22 ` [PATCH 3/5] net/core: Uninline skb_bond() Jay Vosburgh
2008-07-03 1:22 ` [PATCH 4/5] net/core: Allow certain receives on inactive slave Jay Vosburgh
2008-07-03 1:22 ` [PATCH 5/5] net/core: Allow receive on active slaves Jay Vosburgh
2008-07-04 12:45 ` Jeff Garzik
2008-07-06 4:12 ` David Miller
2008-07-06 4:36 ` Joe Eykholt
2008-07-06 4:38 ` David Miller
2008-07-20 4:20 ` Joe Eykholt
2008-08-07 8:00 ` Jeff Garzik [this message]
2008-08-06 22:49 ` [PATCH net-next-2.6 0/5] bonding: Refactor, fix, and updates Jay Vosburgh
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=489AAB91.2000202@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@davemloft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.