From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jens Axboe <axboe@suse.de>
Cc: Tejun Heo <htejun@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] as-iosched: update alias handling
Date: Fri, 11 Nov 2005 09:35:56 +1100 [thread overview]
Message-ID: <4373CB4C.6070602@yahoo.com.au> (raw)
In-Reply-To: <20051110171743.GE3699@suse.de>
Jens Axboe wrote:
> On Thu, Nov 10 2005, Tejun Heo wrote:
>
>>Unlike other ioscheds, as-iosched handles alias by chaing them using
>>rq->queuelist. As aliased requests are very rare in the first place,
>>this complicates merge/dispatch handling without meaningful
>>performance improvement. This patch updates as-iosched to dump
>>aliased requests into dispatch queue as other ioscheds do.
>>
>>Signed-off-by: Tejun Heo <htejun@gmail.com>
>
>
> In theory the way 'as' handles the aliases is faster since we postpone
> pushing them to the dispatch list at the same point (and they have
> strong (if not identical) locality). But it is much simpler to just
> shove the offending requests onto the dispatch list.
>
> It's really up to Nick - what do you think? Leaving patch below.
>
I thought this was pretty cool, but in reality it could be that the
cost / benefit actually goes the wrong way due to added complexity
and rarity of alised requests.
Hmm... I can't bear to ack it ;) I'll close my eyes and let Jens
make the call!
>
>>---
>>
>>Jens, I've tested this change for several hours, but it might be
>>better to postpone this change to next release. It's your call.
>>
It could go into mm now, but probably leave it for 2.6.16 unless
you have some other reason to really need it.
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-11-10 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 14:08 [PATCH] as-iosched: update alias handling Tejun Heo
2005-11-10 17:17 ` Jens Axboe
2005-11-10 22:35 ` Nick Piggin [this message]
2005-11-11 13:21 ` 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=4373CB4C.6070602@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=axboe@suse.de \
--cc=htejun@gmail.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