From: Jay Vosburgh <fubar@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, perex@suse.cz,
oleg@tv-sign.ru, shemminger@linux-foundation.org,
Andy Gospodarek <andy@greyhouse.net>
Subject: Re: [patch 5/7] bonding: replace system timer with work queue
Date: Mon, 26 Mar 2007 23:25:07 -0700 [thread overview]
Message-ID: <25159.1174976707@death> (raw)
In-Reply-To: <20070326215648.58cb392b.akpm@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> wrote:
>On Mon, 26 Mar 2007 21:50:01 -0800 akpm@linux-foundation.org wrote:
>
>> Replace system timer with work queue in monitor functions. The reason for
>> this change is that bonding handlers calls various sleeping functions from
>> the timer handler which is not allowed. Because we cannot share the main
>> workqueue threads (rtnl_lock is used also in linkwatch_event) - new bond
>> workqueue thread is created.
>
>I have a note here that this patch needs additional work.
>
>I forget what it was, there has since been no followup and hence I shall now
>drop this patch.
Andy Gospodarek <andy@greyhouse.net> and I have been working off
list to come up with a comprehensive scheme to resolve the various
locking problems in bonding all at once, rather than piecemeal.
Currently, we believe we've identified all of the problem areas, have
worked up a set of locking rules, and are now hashing out an
implementation that (hopefully) doesn't suck.
The patch referenced above is more or less a functional subset
of the work we're doing, in that we'll also be moving the timers to
workqueues.
Andy, anything to add?
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next prev parent reply other threads:[~2007-03-27 6:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 5:50 [patch 5/7] bonding: replace system timer with work queue akpm
2007-03-27 5:56 ` Andrew Morton
2007-03-27 6:25 ` Jay Vosburgh [this message]
2007-03-27 6:36 ` Jaroslav Kysela
2007-03-27 12:31 ` Andy Gospodarek
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=25159.1174976707@death \
--to=fubar@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=perex@suse.cz \
--cc=shemminger@linux-foundation.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