From: Fabio Checconi <fchecconi@gmail.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Paolo Valente <paolo.valente@unimore.it>,
Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND][RFC] BFQ I/O Scheduler
Date: Thu, 17 Apr 2008 13:30:47 +0200 [thread overview]
Message-ID: <20080417113047.GT62286@gandalf.sssup.it> (raw)
In-Reply-To: <20080417092751.GX12774@kernel.dk>
> From: Jens Axboe <jens.axboe@oracle.com>
> Date: Thu, Apr 17, 2008 11:27:55AM +0200
>
> On Thu, Apr 17 2008, Paolo Valente wrote:
> > Maybe there is also another middle-ground solution. I'll try to sketch
...
> > Does it seem reasonable?
>
> Not for CFQ, that will stay time based. The problem with #2 above is
> that it then quickly turns to various heuristics, which is just
> impossible to tune for general behaviour. Or it just falls apart for
> other real life situations.
>
Ok.
After a brief offline discussion with paolo, here it is what we can do:
o propose a patch for discussion that uses our WF2Q+ variant to
schedule timeslices in cfq. The resulting scheduler would be
quite close to the EEVDF scheduler discussed some time ago for
the cpu.
o Introduce a timeout in bfq to give an upper time limit to the
slices. Since we have not experimented with that mixed approach
before[*], we will need to do some tests with relevant workloads to
see if/how it can work.
I fear that it will take some time, as we're both travelling in this
week.
[*] Anyway it is quite close to how cfq handles async queues, with their
slice_async and slice_async_rq, so it's definitely not something new.
next prev parent reply other threads:[~2008-04-17 11:27 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 [this message]
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
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=20080417113047.GT62286@gandalf.sssup.it \
--to=fchecconi@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@unimore.it \
--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
all inboxes | Powered by JetHome®