From: William Lee Irwin III <wli@holomorphy.com>
To: Jens Axboe <axboe@suse.de>
Cc: Andrew Morton <akpm@digeo.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.5.46-mm2
Date: Sun, 10 Nov 2002 06:52:03 -0800 [thread overview]
Message-ID: <20021110145203.GH23425@holomorphy.com> (raw)
In-Reply-To: <20021110143208.GJ31134@suse.de>
On Sat, Nov 09 2002, Andrew Morton wrote:
>> And Jens's rbtree-based insertion code for the request queue. Which
>> means that the queues can be grown a *lot* if people want to play with
>> that. The VM should be able to cope with it fine.
On Sun, Nov 10, 2002 at 03:32:08PM +0100, Jens Axboe wrote:
> I've attached a small document describing the deadline io scheduler
> tunables. stream_unit is not in Andrew's version, yet, it uses a hard
> defined 128KiB. Also, Andrew didn't apply the rbtree patch only the
> tunable patch. So it uses the same insertion algorithm as the default
> kernel, two linked lists.
Okay, then I'll want the rbtree code for benchmarking.
Thanks,
Bill
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-11-10 14:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 3:59 2.5.46-mm2 Andrew Morton
2002-11-10 14:32 ` 2.5.46-mm2 Jens Axboe
2002-11-10 14:52 ` William Lee Irwin III [this message]
2002-11-10 14:57 ` 2.5.46-mm2 Jens Axboe
2002-11-10 15:06 ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 15:58 ` 2.5.46-mm2 Jens Axboe
2002-11-10 19:39 ` 2.5.46-mm2 Andrew Morton
2002-11-11 1:18 ` 2.5.46-mm2 William Lee Irwin III
2002-11-11 7:04 ` 2.5.46-mm2 Jens Axboe
2002-11-11 7:41 ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 16:58 ` 2.5.46-mm2 Andrew Morton
2002-11-10 17:11 ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 18:14 ` 2.5.46-mm2 - oops Ed Tomlinson
2002-11-10 18:52 ` Andrew Morton
2002-11-10 19:17 ` Ed Tomlinson
2002-11-11 0:44 ` Denis Vlasenko
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=20021110145203.GH23425@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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