From: Jens Axboe <axboe@suse.de>
To: Rui Sousa <rsousa@grad.physics.sunysb.edu>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: Blocked processes <=> Elevator starvation?
Date: Fri, 27 Oct 2000 13:46:03 -0700 [thread overview]
Message-ID: <20001027134603.A513@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0010080105520.22898-100000@duckman.distro.conectiva> <Pine.LNX.4.21.0010271658500.1295-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.21.0010271658500.1295-100000@localhost.localdomain>; from rsousa@grad.physics.sunysb.edu on Fri, Oct 27, 2000 at 05:22:01PM +0100
On Fri, Oct 27 2000, Rui Sousa wrote:
> I finally had time to give this a better look. It now seems the problem
> is in the VM system.
>
> I patched a test10-pre4 kernel with kdb, then started two "diff -ur
> linux-2.4.0testX linux-2.4.0testY > log1" and two "find / -true >
> log". After this I tried cat"ing" a small file. The cat never
> returned. At this point I entered kdb and did a stack trace on the "cat"
> process:
>
> schedule()
> ___wait_on_page()
> do_generic_file_read()
> generic_file_read()
> sys_read()
> system_call()
>
> So it seems the process is either in a loop in ___wait_on_page()
> racing for the PageLock or it never wakes-up... (I guess I could add a
> printk to check which)
> Unfortunately I didn't find anything obviously wrong with the code.
> I hope you can do a better job tracking the problem down.
Rik is right, just because you are seeing long waits on wait_on_page
doesn't make it a vm problem. When a I/O on a page completes, the
page will be unlocked and wait_on_page can grab it -- so I/O stalls
would results in this behaviour.
Could you try this patch:
*.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.0-test10-pre6/blk-7.bz2
and see if it makes a difference?
--
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-27 20:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0010080105520.22898-100000@duckman.distro.conectiva>
2000-10-27 16:22 ` Blocked processes <=> Elevator starvation? Rui Sousa
2000-10-27 16:31 ` Rik van Riel
2000-10-27 20:46 ` Jens Axboe [this message]
2000-10-28 3:14 ` Rui Sousa
2000-10-28 3:27 ` Jens Axboe
2000-10-29 19:21 ` Miles Lane
2000-10-29 22:45 ` Jens Axboe
2000-10-29 22:20 ` Jeff V. Merkey
2000-10-31 0:47 ` Miles Lane
2000-11-03 19:04 ` Jens Axboe
2000-11-06 1:03 ` Giuliano Pochini
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=20001027134603.A513@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=rsousa@grad.physics.sunysb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox