From: Paolo Valente <paolo.valente@unimore.it>
To: Avi Kivity <avi@qumranet.com>
Cc: Jens Axboe <jens.axboe@oracle.com>, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND][RFC] BFQ I/O Scheduler
Date: Thu, 17 Apr 2008 20:12:03 +0200 [thread overview]
Message-ID: <480792F3.8020903@unimore.it> (raw)
In-Reply-To: <480771E5.9070707@qumranet.com>
Avi Kivity ha scritto:
> Paolo Valente wrote:
>> Avi Kivity ha scritto:
>>> Jumping in at random, does "process" here mean task or mms_struct?
>>> If the former, doesn't that mean that a 100-thread process can
>>> starve out a single-threaded process?
>>>
>>> Perhaps we need hierarchical io scheduling, like cfs has for the cpu.
>>>
>> Hierarchical would simplify isolating groups of threads or processes.
>> However, some simple solution is already available with bfq. For
>> example, if you have to fairly share the disk bandwidth between the
>> above 100 threads and another important thread, you get it by just
>> assigning weight 1 to each of these 100 threads, and weight 100 to
>> the important one.
>
> Doesn't work. If the 100-thread process wants to use just on thread
> for issuing I/O, it will be starved by the single-threaded process.
>
> [my example has process A with 100 threads, and process B with 1
> thread, not a 101-thread process with one important thread]
>
Right. I was thinking only about the case where all the 101 threads
concurrently access the disk, and I just wanted to say that weights may
offer more help than priorities in simple cases as this one.
Apart from this, automatically recomputing weights as needed is most
certainly a worse solution than hierarchical scheduling.
Paolo
next prev parent reply other threads:[~2008-04-17 18:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 15:29 Fabio Checconi
2008-04-15 8:22 ` Jens Axboe
2008-04-15 9:11 ` Fabio Checconi
2008-04-15 12:42 ` Jens Axboe
2008-04-15 18:08 ` Fabio Checconi
2008-04-16 6:48 ` Paolo Valente
2008-04-18 1:26 ` Aaron Carroll
2008-04-16 18:44 ` Pavel Machek
2008-04-17 6:14 ` Paolo Valente
2008-04-17 7:10 ` Jens Axboe
2008-04-17 8:26 ` Paolo Valente
2008-04-17 8:30 ` Jens Axboe
2008-04-17 9:24 ` Paolo Valente
2008-04-17 9:27 ` Jens Axboe
2008-04-17 10:19 ` Aaron Carroll
2008-04-17 10:21 ` Jens Axboe
2008-04-17 11:30 ` Fabio Checconi
2008-04-17 15:19 ` Avi Kivity
2008-04-17 15:47 ` Paolo Valente
2008-04-17 15:51 ` Avi Kivity
2008-04-17 18:12 ` Paolo Valente [this message]
2008-04-17 23:44 ` Aaron Carroll
2008-04-17 10:24 ` Aaron Carroll
2008-04-17 11:14 ` Fabio Checconi
2008-04-17 12:14 ` Aaron Carroll
2008-04-17 13:54 ` Jens Axboe
2008-04-17 15:18 ` Paolo Valente
2008-04-17 8:48 ` Pavel Machek
2008-04-17 8:57 ` Jens Axboe
2008-04-17 9:14 ` Fabio Checconi
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=480792F3.8020903@unimore.it \
--to=paolo.valente@unimore.it \
--cc=avi@qumranet.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
Powered by JetHome