From: Lukas Hejtmanek <xhejtman@mail.muni.cz>
To: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ioscheduler and 2.6 kernels
Date: Tue, 22 Nov 2005 13:18:02 +0100 [thread overview]
Message-ID: <20051122121801.GB2529@mail.muni.cz> (raw)
In-Reply-To: <4383078A.5010204@stud.feec.vutbr.cz>
On Tue, Nov 22, 2005 at 12:56:58PM +0100, Michal Schmidt wrote:
> >I have a question about ioschedulers in current 2.6 kernels. Is there an
> >option
> >to build iorequest queues per process? I would like to have the queue for
> >each
> >process and pick up request in round robin manner, which results in more
> >interactive environment.
>
> Isn't this exactly what the CFQ scheduler does?
Friend of me tried all the schedulers and he thinks, that all behave basicaly
the same. His testbed is to extract tar archive with lots small files and in
parallel to run xterm, which takes serious time. He wonder why.
For me it seems to be ok. Thanks.
--
Lukáš Hejtmánek
next prev parent reply other threads:[~2005-11-22 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 11:52 Lukas Hejtmanek
2005-11-22 11:56 ` Michal Schmidt
2005-11-22 12:18 ` Lukas Hejtmanek [this message]
2005-11-22 12:44 ` Jens Axboe
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=20051122121801.GB2529@mail.muni.cz \
--to=xhejtman@mail.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=xschmi00@stud.feec.vutbr.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®