linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: deprogrammer <ttb@tentacle.dhs.org>, linux-mm@kvack.org
Subject: Re: test8-vmpatch performs great here!
Date: Sat, 9 Sep 2000 10:06:33 +0100	[thread overview]
Message-ID: <20000909100633.A8526@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0009082027060.1049-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Fri, Sep 08, 2000 at 08:29:43PM -0300

Hi,

On Fri, Sep 08, 2000 at 08:29:43PM -0300, Rik van Riel wrote:

> This seems to be due to kflushd (bdflush) waking up
> tasks in LIFO order ...

Hmm??

> >From fs/buffer.c:
> 
> in wakeup_bdflush()
>    2435         __set_current_state(TASK_UNINTERRUPTIBLE);
>    2436         add_wait_queue(&bdflush_done, &wait);

> (which adds our task to the front of the wait queue)

Right, but it is TASK_UNINTERRUPTIBLE, not TASK_EXCLUSIVE.

> and in kflushd()
>    2622                 wake_up(&bdflush_done);
> 
> (which wakes up the first task on the wait queue)

No.  That might be true if we were TASK_EXCLUSIVE, but we are not ---
*all_ processes on the wait queue will be woken, and the scheduler
doesn't care in the slightest about which order they get woken in.  It
will just schedule the best process next time.
 
wake_up_all() is only different from wake_up() when you encounter
TASK_EXCLUSIVE processes.

Cheers,
 Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-09-09  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-08 23:20 deprogrammer
2000-09-08 23:29 ` Rik van Riel
2000-09-09  9:06   ` Stephen C. Tweedie [this message]
2000-09-09 22:12     ` Rik van Riel
2000-09-08 23:58 ` Martin Josefsson

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=20000909100633.A8526@redhat.com \
    --to=sct@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    --cc=ttb@tentacle.dhs.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