From: Chris Snook <csnook@redhat.com>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, CK Mailinglist <ck@vds.kolivas.org>
Subject: Re: [ANNOUNCE] DeskOpt - on fly task, i/o scheduler optimization
Date: Fri, 31 Aug 2007 18:26:54 -0400 [thread overview]
Message-ID: <46D895AE.8060308@redhat.com> (raw)
In-Reply-To: <46D8354A.3030208@googlemail.com>
Michal Piotrowski wrote:
> Hi,
>
> Here is something that might be useful for gamers and audio/video editors
> http://www.stardust.webpages.pl/files/tools/deskopt/
>
> You can easily tune CFS/CFQ scheduler params
I would think that gamers and AV editors would want to be using deadline
(or maybe even as), not cfq. How well does it work with other I/O
schedulers?
-- Chris
next prev parent reply other threads:[~2007-08-31 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 15:35 [ANNOUNCE] DeskOpt - on fly task, i/o scheduler optimization Michal Piotrowski
2007-08-31 17:39 ` Arjan van de Ven
2007-08-31 18:07 ` Michal Piotrowski
2007-08-31 22:26 ` Chris Snook [this message]
2007-08-31 23:13 ` Michal Piotrowski
2007-09-01 22:10 ` Andi Kleen
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=46D895AE.8060308@redhat.com \
--to=csnook@redhat.com \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).