From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Al Boldi <a1426z@gawab.com>
Cc: Jens Axboe <axboe@suse.de>,
linux-kernel@vger.kernel.org, David Chinner <dgc@sgi.com>
Subject: Re: [PATCH] Direct I/O bio size regression
Date: Tue, 25 Apr 2006 17:52:43 +1000 [thread overview]
Message-ID: <444DD54B.7010908@yahoo.com.au> (raw)
In-Reply-To: <200604242359.14192.a1426z@gawab.com>
Al Boldi wrote:
> Jens Axboe wrote:
>
>>On Mon, Apr 24 2006, Al Boldi wrote:
>>
>>>On my system max_hw_sectors_kb is fixed at 1024, and max_sectors_kb
>>>defaults to 512, which leads to terribly fluctuating thruput.
>>>
>>>Setting max_sectors_kb = max_hw_sectors_kb makes things even worse.
>>>
>>>Tuning max_sectors_kb to ~192 only stabilizes this situation.
>>
>>That sounds pretty strange. Do you have a test case?
>
>
> I would think that, if you could get your hands on some hw that defaults to
> the same values, you may easily see the same problem by doing this:
>
> 1. # vmstat 1 (or some other bio mon)
> 2. < change vt >
> 3. # cat /dev/hda > /dev/null &
> 4. # cat /dev/hda > /dev/null
> Let this second cat run for a sec, then ^C.
> Depending on your hw specifics the bio should either go up or down by a
> factor of 2 (on my system 25mb/s-48mb/s). You may have to repeat step 4 a
> few times to aggravate the situation.
>
> Note that this is not specific to cat, but can also be observed during normal
> random disk access, although not in a controlled manner.
*random* disk access?
What io scheduler are you using? Can you try with as?
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-04-25 8:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 17:06 [PATCH] Direct I/O bio size regression Al Boldi
2006-04-24 19:49 ` Jens Axboe
2006-04-24 20:59 ` Al Boldi
2006-04-25 7:52 ` Nick Piggin [this message]
2006-04-25 10:45 ` Al Boldi
-- strict thread matches above, loose matches on Subject: below --
2006-04-24 6:14 David Chinner
2006-04-24 7:02 ` Jens Axboe
2006-04-24 9:05 ` Jens Axboe
2006-04-24 14:56 ` David Chinner
2006-04-24 18:47 ` Jens Axboe
2006-04-26 2:30 ` David Chinner
2006-04-26 5:28 ` Jens Axboe
2006-04-26 15:41 ` David Chinner
2006-04-26 17:55 ` Jens Axboe
2006-05-07 16:25 ` Lee Revell
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=444DD54B.7010908@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=a1426z@gawab.com \
--cc=axboe@suse.de \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.