public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.6-rc3-mm2
Date: Wed, 5 May 2004 08:59:06 -0700	[thread overview]
Message-ID: <20040505155906.GN1397@holomorphy.com> (raw)
In-Reply-To: <4098DB41.1A7FC5DF@tv-sign.ru>

On Wed, May 05, 2004 at 04:17:05PM +0400, Oleg Nesterov wrote:
> also, exclusive wakeups have no problems, and process
> waiting in wait_on_page_writeback() won't be waken
> by unlock_page(). it will be waken _only_ when that
> bit will be cleared.

I didn't feel obligated to answer the last time since I suspected you'd
not press the issue after realizing the error.

The object isn't passed down to the wake function at all, so it can't
avoid falsely scheduling waiters on the wrong objects and/or bits.


-- wli

  reply	other threads:[~2004-05-05 15:59 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-05 11:28 2.6.6-rc3-mm2 Oleg Nesterov
2004-05-05 12:17 ` 2.6.6-rc3-mm2 Oleg Nesterov
2004-05-05 15:59   ` William Lee Irwin III [this message]
2004-05-05 17:17     ` 2.6.6-rc3-mm2 Oleg Nesterov
     [not found] <fa.gcf87gs.1sjkoj6@ifi.uio.no>
     [not found] ` <fa.freqmjk.11j6bhe@ifi.uio.no>
2004-05-08 19:29   ` 2.6.6-rc3-mm2 Andy Lutomirski
2004-05-09 13:32     ` 2.6.6-rc3-mm2 Andi Kleen
2004-05-09 22:16       ` 2.6.6-rc3-mm2 Rusty Russell
2004-05-10  5:40         ` 2.6.6-rc3-mm2 Andi Kleen
2004-05-10 10:48           ` 2.6.6-rc3-mm2 Rusty Russell
2004-05-10  9:59         ` 2.6.6-rc3-mm2 Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2004-05-05 19:10 2.6.6-rc3-mm2 Jan Killius
2004-05-05  8:31 2.6.6-rc3-mm2 Andrew Morton
2004-05-05  8:46 ` 2.6.6-rc3-mm2 Fabio Coatti
2004-05-05  9:07 ` 2.6.6-rc3-mm2 Onur Kucuk
2004-05-05 15:33 ` 2.6.6-rc3-mm2 Christoph Hellwig
2004-05-05 17:59   ` 2.6.6-rc3-mm2 Arnd Bergmann
2004-05-05 16:06 ` 2.6.6-rc3-mm2 Paul Jackson
2004-05-05 16:40   ` 2.6.6-rc3-mm2 Christoph Hellwig
2004-05-05 16:49     ` 2.6.6-rc3-mm2 Paul Jackson
2004-05-05 20:16   ` 2.6.6-rc3-mm2 R. J. Wysocki
2004-05-06  1:51     ` 2.6.6-rc3-mm2 Paul Jackson
2004-05-06 19:38       ` 2.6.6-rc3-mm2 R. J. Wysocki
2004-05-06 14:53 ` 2.6.6-rc3-mm2 Antonio Dolcetta
2004-05-06 15:12   ` 2.6.6-rc3-mm2 Andrew Morton
2004-05-06 15:56     ` 2.6.6-rc3-mm2 Antonio Dolcetta
2004-05-06 17:26       ` 2.6.6-rc3-mm2 Adrian Bunk
2004-05-06 21:46 ` 2.6.6-rc3-mm2 Bruce Guenter
2004-05-07  2:52   ` 2.6.6-rc3-mm2 Andrew Morton
2004-05-07  4:16     ` 2.6.6-rc3-mm2 Rusty Russell
2004-05-07 16:05       ` 2.6.6-rc3-mm2 Bruce Guenter
2004-05-07 20:13       ` 2.6.6-rc3-mm2 R. J. Wysocki
2004-05-08  6:09         ` 2.6.6-rc3-mm2 Andrew Morton
     [not found]           ` <200405081329.43017.rjwysocki@sisk.pl>
2004-05-08 11:31             ` 2.6.6-rc3-mm2 Andrew Morton
2004-05-08 16:25               ` 2.6.6-rc3-mm2 R. J. Wysocki
2004-05-08 11:43             ` 2.6.6-rc3-mm2 Andrew Morton
2004-05-08 12:16               ` 2.6.6-rc3-mm2 R. J. Wysocki
2004-05-08 16:59           ` 2.6.6-rc3-mm2 Bruce Guenter
2004-05-08 18:46             ` 2.6.6-rc3-mm2 Andrew Morton
2004-05-08 18:31 ` 2.6.6-rc3-mm2 Joseph Fannin

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=20040505155906.GN1397@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@tv-sign.ru \
    /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