From: Jens Axboe <axboe@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] Time sliced cfq ver14
Date: Wed, 15 Dec 2004 13:03:27 +0100 [thread overview]
Message-ID: <20041215120323.GT3157@suse.de> (raw)
In-Reply-To: <20041215082004.GO3157@suse.de>
Hi,
2.6.10-rc3-mm1 patch:
http://www.kernel.org/pub/linux/kernel/people/axboe/patches/v2.6/2.6.10-rc3-mm1/cfq-time-slices-14-2.6.10-rc3-mm1.gz
2.6-BK patch:
http://www.kernel.org/pub/linux/kernel/people/axboe/patches/v2.6/2.6.10-rc3/cfq-time-slices-14.gz
Changes:
- Fix leak of queue
- Better balance when to preempt. On 8 client read workload, aggregate
bandwidth would take a few seconds to build up, due to initial massive
preempt generation more seeks than it should. Priority check was also
reverse which showed bad results on multi-prio work loads.
- Fix reversed priority check in preemption check, oops.
--
Jens Axboe
next prev parent reply other threads:[~2004-12-15 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 8:20 [PATCH] Time sliced cfq ver13 Jens Axboe
2004-12-15 12:03 ` Jens Axboe [this message]
2004-12-16 15:34 ` [PATCH] Time sliced cfq ver17 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=20041215120323.GT3157@suse.de \
--to=axboe@suse.de \
--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