From: Alexandru Moise <00moses.alexander00@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cfq-iosched: convert slice idle time to jiffies
Date: Tue, 29 Dec 2015 18:33:02 +0100 [thread overview]
Message-ID: <20151229173302.GA13345@gmail.com> (raw)
In-Reply-To: <5682C095.70002@kernel.dk>
On Tue, Dec 29, 2015 at 10:19:17AM -0700, Jens Axboe wrote:
> On 12/28/2015 06:08 PM, Alexandru Moise wrote:
> >This patch refers to Jens Axboe's change way back in 2006:
> >7b14e3b52 cfq-iosched: slice expiry fixups
> >
> >In this patch he fixed a potential timer race condition by delaying
> >idle_slice_timer by the slice_idle time value.
> >
> >Today this timer is delayed by either slice_idle or group_idle time
> >values, which on my system, and according to
> >Documentation/block/cfq-iosched.txt the default value for both is 8ms.
> >
> >Since the time given by either variables is supposed to be in
> >milliseconds we should convert that value from milliseconds to jiffies
> >before adding it to jiffies variable and setting our timer.
> >
> >In my obervations the area is really active as I've seen that function
> >get called a lot for each device on my btrfs raid setup during btrfs
> >check. I've also timed the btrfs check before and after applying the
> >patch and I might've noticed a very slight improvement in execution
> >time but the numbers vary too much for me to post any believable
> >numbers (10 milliseconds difference at most on average).
>
> cfqd->cfq_slice_idle is in jiffies, it's not in msecs.
>
> --
> Jens Axboe
>
Then should I only do the conversion in the case of group_idle?
prev parent reply other threads:[~2015-12-29 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 1:08 [PATCH] cfq-iosched: convert slice idle time to jiffies Alexandru Moise
2015-12-29 17:19 ` Jens Axboe
2015-12-29 17:33 ` Alexandru Moise [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=20151229173302.GA13345@gmail.com \
--to=00moses.alexander00@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--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.