public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giuliano Pochini <pochini@denise.shiny.it>
To: Miles Lane <miles@speakeasy.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Blocked processes <=> Elevator starvation?
Date: Sun, 05 Nov 2000 20:03:19 -0500	[thread overview]
Message-ID: <3A060357.BE2C381E@denise.shiny.it> (raw)
In-Reply-To: <20001027134603.A513@suse.de> <Pine.LNX.4.21.0010280408520.1157-100000@localhost.localdomain> <20001027202710.A825@suse.de> <39FC78BF.90607@speakeasy.org> <20001029144543.D615@suse.de> <39FE16A3.5070608@speakeasy.org>



> I just reproduced the problem in test10-pre7.  Here's the
> output you requested:
> 
> vmstat 1
>     procs                      memory    swap          io     system         cpu
>   r  b  w   swpd   free   buff  cache  si  so    bi    bo   in    cs  us  sy  id
>   0  2  2      0  45764  76000  59520   0   0     0   509  272   508   0   0 100
>   0  2  2      0  45300  76324  59520   0   0     0   636  276   548   1   0  99
>   0  2  2      0  44896  76680  59520   0   0     0   636  273   523   0   0 100
>   0  2  2      0  44088  77392  59520   0   0     0   650  281  1307   0   7  93
>   1  1  2      0  43736  77680  59548   0   0     0  1279  908  2637   1   8  91
>   0  2  3      0  43072  78040  59592   0   0     0  1660 1281  4119   5   6  89
> 
>  >>> /var/log/kernel output stopped being emitted here <<<
>  >>>  CRUNCH!  <<<
> 
>   0  2  3      0  42656  78384  59592   0   0     0   259  271   551   0   0 100
>   0  2  3      0  42656  78384  59592   0   0     0     5  271   499   0   0 100
>   0  2  3      0  42656  78384  59592   0   0     0     5  272   511   0   2  98
>   0  2  3      0  42656  78384  59592   0   0     0     4  268   502   0   0 100
>   0  2  3      0  42656  78384  59592   0   0     0     5  272   508   0   0 100
>   0  2  3      0  42656  78384  59592   0   0     0     5  274   523   0   0 100


test7 had the problem that when the rq queue if full new requests are no
longer
merged together (the disk is slow because it writes a lot of 512 bytes blocks
instead of 128K blocks).  There is a patch for this. There still is the
problem that when the rq queue if full other processes can no more access to
*any*
device that uses ll_rw_block() and they remain blocked in D state.


Bye.


-
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/

      parent reply	other threads:[~2000-11-07 20:52 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
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 [this message]

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=3A060357.BE2C381E@denise.shiny.it \
    --to=pochini@denise.shiny.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@speakeasy.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