From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Tejun Heo <htejun@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Alex Chiang <achiang@hp.com>, <greg@kroah.com>,
<kay.sievers@vrfy.org>, <rusty@rustcorp.com.au>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/3] sysfs: allow suicide
Date: Thu, 26 Mar 2009 15:56:09 +0100 [thread overview]
Message-ID: <20090326155609.56a662cf@gondolin> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0903261005530.2945-100000@iolanthe.rowland.org>
On Thu, 26 Mar 2009 10:21:23 -0400 (EDT),
Alan Stern <stern@rowland.harvard.edu> wrote:
> The idea is that this would come in useful both for suicidal sysfs
> attributes and for hot-unplug events detected by an interrupt handler.
Yes; the ccw bus uses it's own workqueue, so it doesn't need
device_schedule_callback() to commit suicide. I guess other busses
could do the same.
>
> But there's something I'm not clear on. If hot-unplug events are
> detected by an interrupt handler, then what about hot-plug events?
> Wouldn't they be detected by the same interrupt handler? Obviously you
> can't register new devices in interrupt context, so there must be a
> workqueue or kernel thread involved somewhere. Shouldn't the two types
> of events be managed by the same workqueue/thread?
They should, you want to serialize plug/unplug. You'll even want to use
the same queue for plug/unplug not detected in interrupt context.
The next question is how granular those workqueues should be. Per
subsystem? Per bus? Something else?
next prev parent reply other threads:[~2009-03-26 14:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 4:16 [RFC PATCH 0/3] sysfs: allow suicide Alex Chiang
2009-03-25 4:16 ` [RFC PATCH 1/3] sysfs: make the sysfs_addrm_cxt->removed list FIFO Alex Chiang
2009-03-25 4:16 ` [RFC PATCH 2/3] sysfs: add blocking notifier to prohibit module unload Alex Chiang
2009-03-25 4:17 ` [RFC PATCH 3/3] sysfs: care-free suicide for sysfs files Alex Chiang
2009-03-26 5:24 ` Tejun Heo
2009-03-25 5:54 ` [RFC PATCH 0/3] sysfs: allow suicide Eric W. Biederman
2009-03-25 22:54 ` Alex Chiang
2009-03-26 0:42 ` Eric W. Biederman
2009-03-26 1:26 ` Alex Chiang
2009-03-26 2:41 ` Eric W. Biederman
2009-03-26 1:32 ` Tejun Heo
2009-03-26 3:05 ` Eric W. Biederman
2009-03-26 3:36 ` Tejun Heo
2009-03-26 14:21 ` Alan Stern
2009-03-26 14:56 ` Cornelia Huck [this message]
2009-03-25 14:45 ` Alan Stern
2009-03-25 23:03 ` Alex Chiang
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=20090326155609.56a662cf@gondolin \
--to=cornelia.huck@de.ibm.com \
--cc=achiang@hp.com \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=htejun@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=stern@rowland.harvard.edu \
/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.