From: Jens Axboe <axboe@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Mike Galbraith <efault@gmx.de>, Andrew Morton <akpm@osdl.org>,
ck@vds.kolivas.org, linux-kernel@vger.kernel.org
Subject: Re: [ck] Re: [PATCH] mm: Implement swap prefetching tweaks
Date: Tue, 14 Mar 2006 09:05:27 +0100 [thread overview]
Message-ID: <20060314080527.GC4419@suse.de> (raw)
In-Reply-To: <1142319048.13256.103.camel@mindpipe>
On Tue, Mar 14 2006, Lee Revell wrote:
> On Tue, 2006-03-14 at 07:40 +0100, Mike Galbraith wrote:
> > On Sat, 2006-03-11 at 23:54 -0500, Lee Revell wrote:
> > > On Sat, 2006-03-11 at 08:51 +0100, Mike Galbraith wrote:
> > > > There used to be a pages in flight 'restrictor plate' in there that
> > > > would have probably helped this situation at least a little. But in
> > > > any case, it sounds like you'll have to find a way to submit the IO in
> > > > itty bitty synchronous pieces.
> > >
> > > echo 64 > /sys/block/hd*/queue/max_sectors_kb
> > >
> > > There is basically a straight linear relation between whatever you set
> > > this to and the maximum scheduling latency you see. It was developed to
> > > solve the exact problem you are describing.
> >
> > <head-scratching>
> >
> > Is it possible that you mean pci latency? I'm unable to measure any
> > scheduling latency > 5ms while pushing IO for all my little Barracuda
> > disk is worth.
>
> It's only a big problem if LBA48 is in use which allows 32MB of IO to be
> in flight at once, this depends on the size of the drive.
>
> What does that value default to?
Not quite true. Even if lba48 is active on the drive, we don't allow
more than 1MB per request. And nit picking a little, lba48 doesn't
always depend on the size of the drive, some drives smaller than 2^28
sectors also feature lba48 support.
--
Jens Axboe
prev parent reply other threads:[~2006-03-14 8:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 9:54 [PATCH] mm: Implement swap prefetching tweaks Con Kolivas
2006-03-10 22:35 ` Andrew Morton
2006-03-10 23:11 ` Peter Williams
2006-03-11 4:18 ` Con Kolivas
2006-03-11 4:28 ` Peter Williams
2006-03-11 4:34 ` Con Kolivas
2006-03-11 5:34 ` Peter Williams
2006-03-11 5:04 ` [ck] " Radoslaw Szkodzinski
2006-03-11 5:21 ` Con Kolivas
2006-03-11 5:46 ` Peter Williams
2006-03-11 3:50 ` Con Kolivas
2006-03-11 5:33 ` Mike Galbraith
2006-03-11 5:50 ` Con Kolivas
2006-03-11 5:58 ` Con Kolivas
2006-03-11 6:11 ` Mike Galbraith
2006-03-11 6:00 ` Mike Galbraith
2006-03-11 6:05 ` Mike Galbraith
2006-03-11 7:20 ` Con Kolivas
2006-03-11 7:44 ` Mike Galbraith
2006-03-11 8:16 ` Nick Piggin
2006-03-11 8:22 ` Mike Galbraith
2006-03-11 7:24 ` Con Kolivas
2006-03-11 7:51 ` Mike Galbraith
2006-03-11 8:15 ` Con Kolivas
2006-03-12 4:54 ` Lee Revell
2006-03-12 5:27 ` Mike Galbraith
2006-03-12 8:36 ` Con Kolivas
2006-03-14 6:40 ` Mike Galbraith
2006-03-14 6:50 ` Lee Revell
2006-03-14 7:06 ` Mike Galbraith
2006-03-14 8:44 ` Mike Galbraith
2006-03-14 8:05 ` Jens Axboe [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=20060314080527.GC4419@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=ck@vds.kolivas.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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;
as well as URLs for NNTP newsgroup(s).