From: Tim Hockin <thockin@hockin.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Tim Hockin <thockin@Sun.COM>,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: calling flush_scheduled_work()
Date: Fri, 12 Mar 2004 14:38:11 -0800 [thread overview]
Message-ID: <20040312223811.GA15636@hockin.org> (raw)
In-Reply-To: <1079128848.3166.44.camel@lade.trondhjem.org>
On Fri, Mar 12, 2004 at 05:00:48PM -0500, Trond Myklebust wrote:
> It would be dead easy to change RPC+NFS to use their own, workqueue. In
> fact I've already considered that several times in the places where the
> NFSv4 state stuff gets hairy. ... but it might be nice not to have to
> set up all these (mostly) idle threads for exclusive use by NFS just in
> order to catch a corner case.
>
> Could we therefore perhaps consider setting up one or more global
> workqueues that would be alternatives to keventd?
That just divides up the problem, but doesn't solve it. The simplest would
be to print a badness and somehow get out of the flush. Then anyone who is
triggering the corner case (us, in this case) can just solve it ourselves.
It's not pretty.
In short, it's dubious that ANYONE call flush_scheduled_work() on a
workqueue that they don't own.
Tim
next prev parent reply other threads:[~2004-03-12 22:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 20:58 calling flush_scheduled_work() Tim Hockin
2004-03-12 22:00 ` Trond Myklebust
2004-03-12 22:38 ` Tim Hockin [this message]
2004-03-12 23:19 ` Trond Myklebust
2004-03-12 23:27 ` Tim Hockin
2004-03-12 23:27 ` Andrew Morton
2004-03-13 0:20 ` Tim Hockin
2004-03-13 1:17 ` Trond Myklebust
2004-03-13 2:12 ` Andrew Morton
2004-03-13 2:24 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2004-03-13 11:45 Stefan Rompf
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=20040312223811.GA15636@hockin.org \
--to=thockin@hockin.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@Sun.COM \
--cc=trond.myklebust@fys.uio.no \
/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