From: Jeff Moyer <jmoyer@redhat.com>
To: Corrado Zoccolo <czoccolo@gmail.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [RFC V2 PATCH 1/5] cfq-iosched: adapt slice to number of processes doing I/O
Date: Wed, 21 Oct 2009 12:36:49 -0400 [thread overview]
Message-ID: <x49tyxs7lge.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <4e5e476b0910210932l2dffdabdv67a449ca162efd0f@mail.gmail.com> (Corrado Zoccolo's message of "Wed, 21 Oct 2009 18:32:37 +0200")
Corrado Zoccolo <czoccolo@gmail.com> writes:
>> Couldn't you have just divided the slice by iq? And why iq? Why not
>> nr_qs or avg_qlen or something? It's a minor nit; I can live with it.
>
> iq stands for interested queues, because we are restricting the count
> just to the same priority class, not all queues in the system.
Ah, that makes sense. A comment would make that clear.
> I don't think this is equivalent. You seem to compute some divisions
> too early, losing in precision.
OK, I figured as much.
> slice * cfq_target_latency / (cfqd->cfq_slice[1] * iq)
> is not generally equivalent to:
> slice * (cfq_target_latency / (cfqd->cfq_slice[1] * iq))
> that is what you are computing.
> There is an other such case in your simplification.
OK. The idea was to try to make the thing a bit more digestable.
Honestly, I had to re-write it to figure out what it was doing. Could
you rework it so the logic is more obvious to others and still correct?
Thanks!
Jeff
next prev parent reply other threads:[~2009-10-21 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 18:11 Corrado Zoccolo
2009-10-21 15:16 ` Jeff Moyer
2009-10-21 15:57 ` Jeff Moyer
2009-10-21 16:32 ` Corrado Zoccolo
2009-10-21 16:36 ` Jeff Moyer [this message]
2009-10-22 10:43 ` Corrado Zoccolo
2009-10-26 15:10 ` Jeff Moyer
2009-10-26 15:14 ` Corrado Zoccolo
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=x49tyxs7lge.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=czoccolo@gmail.com \
--cc=jens.axboe@oracle.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
all inboxes | Powered by JetHome®