public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Rene Herman <rene.herman@gmail.com>,
	Andrew Morton <akpm@osdl.org>, Tejun Heo <htejun@gmail.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: 2.6.20-rc2+: CFQ halving disk throughput.
Date: Tue, 02 Jan 2007 10:12:06 -0500	[thread overview]
Message-ID: <459A7646.1070007@rtr.ca> (raw)
In-Reply-To: <20070102121048.GU2483@kernel.dk>

Jens Axboe wrote:
> On Tue, Jan 02 2007, Jens Axboe wrote:
>> On Tue, Jan 02 2007, Rene Herman wrote:
>>> Jens Axboe wrote:
>>>
>>>> On Mon, Jan 01 2007, Andrew Morton wrote:
>>>>> The patch would appear to need this fix:
>>>>>
>>>>> --- a/block/cfq-iosched.c~a
>>>>> +++ a/block/cfq-iosched.c
>>>>> @@ -592,7 +592,7 @@ static int cfq_allow_merge(request_queue
>>>>> 	if (cfqq == RQ_CFQQ(rq))
>>>>> 		return 1;
>>>>>
>>>>> -	return 1;
>>>>> +	return 0;
>>>>> }
>>>>>
>>>>> static inline void
>>>>> _
>>>>>
>>>>> But that might not fix things...
>>>> Yeah it is, but I don't think it'll fix it (if anything, it'll be more
>>>> conservative).
>>> (to possibly save others from trying -- no, doesn't fix any)
>> As expected. The issue is rq_is_sync(rq) takes the data direction into
>> account as well, while bio_sync() only checks the sync bit. This should
>> fix it.
> 
> And here a little more relaxed version, as Mark Lord suggested. We allow
> merge of async bio into a sync request, but not vice versa.
> 
> Both patches pending testing, will do so now.

Performance is right back where it should be now, thanks!

I did have to massage the second patch to get it to apply cleanly
after the first patch.  You may want to regenerate it against -rc3.

Cheers

  reply	other threads:[~2007-01-02 15:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 13:37 PATA -- pata_amd on 2.6.19 fails to IDENTIFY my DVD-ROM Rene Herman
2006-12-27  7:19 ` Tejun Heo
2006-12-27 17:50   ` Rene Herman
2006-12-28  2:24     ` Tejun Heo
2007-01-01 22:46       ` 2.6.20-rc2+: CFQ halving disk throughput Rene Herman
2007-01-01 22:56         ` Rene Herman
2007-01-01 23:30           ` Linus Torvalds
2007-01-01 23:28         ` Mark Lord
2007-01-02  8:34           ` Jens Axboe
2007-01-02 15:01             ` Mark Lord
2007-01-02 16:53               ` Tejun Heo
2007-01-02 17:35                 ` Mark Lord
2007-01-02 17:53                   ` Tejun Heo
2007-01-02 18:10                     ` Mark Lord
2007-01-02 17:09               ` Jan Engelhardt
2007-01-02  5:36         ` Andrew Morton
2007-01-02  8:44           ` Jens Axboe
2007-01-02 10:24             ` Rene Herman
2007-01-02 11:57               ` Jens Axboe
2007-01-02 12:10                 ` Jens Axboe
2007-01-02 15:12                   ` Mark Lord [this message]
2007-01-02 15:14                     ` Jens Axboe
2007-01-02 15:40                       ` Mark Lord
2007-01-02 15:45                         ` 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=459A7646.1070007@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=htejun@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@gmail.com \
    --cc=torvalds@osdl.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