From: Jens Axboe <jens.axboe@oracle.com>
To: Corrado Zoccolo <czoccolo@gmail.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
Jeff Moyer <jmoyer@redhat.com>
Subject: Re: [PATCH v2] cfq-iosched: avoid probable slice overrun when idling
Date: Thu, 8 Oct 2009 08:41:09 +0200 [thread overview]
Message-ID: <20091008064109.GM8703@kernel.dk> (raw)
In-Reply-To: <200910072315.42047.czoccolo@gmail.com>
On Wed, Oct 07 2009, Corrado Zoccolo wrote:
> Idle timer is not armed if remaining slice is less than average think
> time.
Thanks, this looks a lot more appropriate. I will commit it, but expand
your changelog somewhat. The changelog needs to always explain the
rationale behind the change, this one is a bit on the terse side.
--
Jens Axboe
prev parent reply other threads:[~2009-10-08 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 8:59 [PATCH] cfq-iosched: avoid slice overrun when idling Corrado Zoccolo
2009-10-07 17:51 ` Jens Axboe
2009-10-07 19:30 ` Corrado Zoccolo
2009-10-07 21:15 ` [PATCH v2] cfq-iosched: avoid probable " Corrado Zoccolo
2009-10-08 6:41 ` Jens Axboe [this message]
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=20091008064109.GM8703@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=czoccolo@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.