From: Lee Revell <rlrevell@joe-job.com>
To: David Chinner <dgc@sgi.com>
Cc: Jens Axboe <axboe@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Direct I/O bio size regression
Date: Sun, 07 May 2006 12:25:45 -0400 [thread overview]
Message-ID: <1147019145.15364.236.camel@mindpipe> (raw)
In-Reply-To: <20060426023031.GH611708@melbourne.sgi.com>
On Wed, 2006-04-26 at 12:30 +1000, David Chinner wrote:
> Got any data that you can share with us?
>
The thread was from July 2004 and was called:
Re: [linux-audio-dev] Re: [announce]
[patch] Voluntary Kernel Preemption
Patch
Also some info in thread:
Re: [patch]
voluntary-preempt-2.6.8-rc2-M5
> Wrt latency, is the problem to do with large requests causing short
> term latency? I thought that latency minimisation is the job of the
> I/O scheduler, so if this is the case, doesn't this indicate a
> deficiency of the I/O scheduler? e.g. the I/o scheduler could split
> large requests to reduce latency, just like you merge adjacent
> requests to reduce the number of I/Os and keep overall latency
> low...
>
I think you are talking past each other - Jens is referring to scheduler
latency, not IO latency.
Lee
next prev parent reply other threads:[~2006-05-07 16:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 6:14 [PATCH] Direct I/O bio size regression 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-24 17:06 Al Boldi
2006-04-24 19:49 ` Jens Axboe
2006-04-24 20:59 ` Al Boldi
2006-04-25 7:52 ` Nick Piggin
2006-04-25 10:45 ` Al Boldi
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=1147019145.15364.236.camel@mindpipe \
--to=rlrevell@joe-job.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox