From: Andrew Morton <akpm@zip.com.au>
To: William Lee Irwin III <wli@holomorphy.com>,
linux-kernel@vger.kernel.org, riel@surriel.com, mjc@kernel.org,
bcrl@redhat.com
Subject: Re: hashed waitqueues
Date: Fri, 04 Jan 2002 15:21:55 -0800 [thread overview]
Message-ID: <3C363913.DA9CABCF@zip.com.au> (raw)
In-Reply-To: <20020104094049.A10326@holomorphy.com> <3C3635A8.447EE52E@zip.com.au>
Andrew Morton wrote:
>
> > + /*
> > + * Although the default semantics of wake_up() are
> > + * to wake all, here the specific function is used
> > + * to make it even more explicit that a number of
> > + * pages are being waited on here.
> > + */
> > + if(waitqueue_active(page_waitqueue(page)))
> > + wake_up_all(page_waitqueue(page));
> ...
>
> Also, why wake_up_all()? That will wake all tasks which are sleeping
> in __lock_page(), even though they've asked for exclusive wakeup
> semantics. Will a bare wake_up() here not suffice?
>
Doh. It helps to read the comment. Suggest that __lock_page()
be changed to use add_wait_queue().
-
next prev parent reply other threads:[~2002-01-04 23:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 17:40 hashed waitqueues William Lee Irwin III
2002-01-04 21:47 ` Momchil Velikov
2002-01-04 23:07 ` Andrew Morton
2002-01-04 23:21 ` Andrew Morton [this message]
2002-01-04 23:48 ` William Lee Irwin III
2002-01-05 0:37 ` Daniel Phillips
2002-01-05 1:39 ` William Lee Irwin III
2002-01-05 2:44 ` Daniel Phillips
2002-01-05 5:06 ` William Lee Irwin III
2002-01-08 18:20 ` William Lee Irwin III
2002-01-08 18:27 ` William Lee Irwin III
[not found] ` <523d1gu1ni.fsf@love-boat.topspincom.com>
2002-01-08 18:44 ` William Lee Irwin III
2002-01-08 19:20 ` Hugh Dickins
2002-01-08 20:19 ` William Lee Irwin III
2002-01-16 14:21 ` Jamie Lokier
2002-01-16 17:42 ` William Lee Irwin III
2002-01-18 0:34 ` Jamie Lokier
2002-01-06 21:09 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2002-01-04 21:17 Ed Tomlinson
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=3C363913.DA9CABCF@zip.com.au \
--to=akpm@zip.com.au \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjc@kernel.org \
--cc=riel@surriel.com \
--cc=wli@holomorphy.com \
/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