linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] cfq: always return false from should_idle if slice_idle is set to zero
Date: Mon, 28 Jun 2010 20:50:44 +0200	[thread overview]
Message-ID: <4C28EF04.7040309@kernel.dk> (raw)
In-Reply-To: <x49hbkndmoc.fsf@segfault.boston.devel.redhat.com>

On 28/06/10 20.41, Jeff Moyer wrote:
> Jens Axboe <axboe@kernel.dk> writes:
> 
>> On 21/06/10 21.49, Jeff Moyer wrote:
>>> Hi,
>>>
>>> In testing a competing fsync-ing process and a sequential reader on
>>> mid-grade storage, I found that cfq was incapable of achieving the I/O
>>> rates of deadline, no matter how it was tuned.  Investigation, and insight
>>> from Vivek (mostly the latter), led to identifying that we were still
>>> idling for the last queue in the service tree.
>>>
>>> Modifying cfq_should_idle to not idle when slice_idle is set to zero got
>>> us much closer to the performance of deadline for this workload.  I have
>>> one follow-on patch that gets us on-par with deadline, but I think this
>>> patch stands alone.
>>>
>>> Comments, as always, are appreciated.
>>
>> This looks good.
> 
> So.... applied to which branch?

Not applied yet, unless I explicitly say it's applied, then it's not
necessarily in any public git tree yet. But this will go into .35.

-- 
Jens Axboe


  reply	other threads:[~2010-06-28 18:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 19:49 [PATCH 0/2] cfq: fixes to bring cfq in line with deadline performance for mid- to high-end storage Jeff Moyer
2010-06-21 19:49 ` [PATCH 1/2] cfq: always return false from should_idle if slice_idle is set to zero Jeff Moyer
2010-06-21 20:00   ` Jens Axboe
2010-06-28 18:41     ` Jeff Moyer
2010-06-28 18:50       ` Jens Axboe [this message]
2010-06-28 18:54         ` Jeff Moyer
2010-06-21 23:05   ` Vivek Goyal
2010-06-21 19:49 ` [PATCH 2/2] cfq: allow dispatching of both sync and async I/O together Jeff Moyer
2010-06-21 19:59   ` Jens Axboe
2010-06-21 20:05     ` Jeff Moyer
2010-06-21 23:22     ` Vivek Goyal
2010-06-22  4:07       ` Vivek Goyal
2010-06-22 12:45         ` Jeff Moyer
2010-06-22 13:18           ` Vivek Goyal
2010-06-22 13:21             ` Jens Axboe
2010-06-22 14:24               ` Vivek Goyal
2010-06-22 14:27             ` Jeff Moyer
2010-06-28 18:40         ` Jeff Moyer
2010-06-28 18:48           ` 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=4C28EF04.7040309@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=jmoyer@redhat.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;
as well as URLs for NNTP newsgroup(s).