public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: rwhron@earthlink.net
Cc: akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.21 IDE 91
Date: Sat, 15 Jun 2002 19:17:11 +0200	[thread overview]
Message-ID: <20020615171711.GH1359@suse.de> (raw)
In-Reply-To: <20020615104239.GA30698@rushmore>

On Sat, Jun 15 2002, rwhron@earthlink.net wrote:
> > One possibile culprit here is the doubling of the request queue size
> > in 2.5.20.  A long time ago it was 1024 slots.  Then it went to
> > 128.  That's where it is in Marcelo kernels.  Then -ac kernels
> > went up to 1024 because they have read-latency2.  Somehow 2.5 found
> > itself at 256 slots.  In 2.5.20 it slealthily snuck up to 512
> > slots.  I didn't squeak about this because I was interested to see what
> > effect it would have.
> 
> Interesting.  I've seen read-latency2 drop dbench throughput in -aa
> kernels (but I use it anyway).  I'd like to capture the request
> queue size.  Is there a command or file in /proc that displays 
> it, or should I just grep drivers/block/ll_rw_blk.c?

There is currently no way you can capture the queue request state. In
the past I've done sysrq hacks to display it, but that's about it.

-- 
Jens Axboe


  reply	other threads:[~2002-06-15 17:17 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-15 10:42 [PATCH] 2.5.21 IDE 91 rwhron
2002-06-15 17:17 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-18 13:24 rwhron
2002-06-17 13:16 rwhron
2002-06-16 16:36 rwhron
2002-06-16 13:03 rwhron
2002-06-16 11:05 rwhron
2002-06-16 10:52 rwhron
2002-06-15 21:00 rwhron
2002-06-15 21:00 ` William Lee Irwin III
2002-06-15 21:23 ` Andrew Morton
2002-06-15 12:05 rwhron
2002-06-17  8:40 ` Andrew Morton
2002-06-15 11:41 rwhron
2002-06-15 11:50 ` Dave Jones
2002-06-14 18:36 Andries.Brouwer
2002-06-14 17:09 Andries.Brouwer
2002-06-14 17:15 ` Martin Dalecki
2002-06-14 16:29 Hron, Randall
2002-06-14 23:32 ` Andrew Morton
2002-06-09  5:42 Linux 2.5.21 Linus Torvalds
2002-06-14 14:02 ` [PATCH] 2.5.21 IDE 91 Martin Dalecki
2002-06-14 15:17   ` Jens Axboe
2002-06-14 15:42     ` John Weber
2002-06-14 15:43     ` Dave Jones
2002-06-14 16:06       ` Bartlomiej Zolnierkiewicz
2002-06-14 16:33         ` Martin Dalecki
2002-06-14 17:56       ` Linus Torvalds
2002-06-14 15:56     ` Benjamin LaHaise
2002-06-14 16:04       ` Dave Jones
2002-06-14 17:23         ` Martin Dalecki
2002-06-14 16:09       ` Bartlomiej Zolnierkiewicz
2002-06-14 16:15     ` Martin Dalecki
2002-06-15  8:15       ` Jens Axboe
2002-06-14 16:43     ` Linus Torvalds
2002-06-14 16:47       ` Martin Dalecki
2002-06-15  8:19       ` Jens Axboe

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=20020615171711.GH1359@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rwhron@earthlink.net \
    /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