From: Bernardo Innocenti <bernie@develer.com>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make I/O schedulers optional
Date: Sun, 27 Jul 2003 17:36:05 +0200 [thread overview]
Message-ID: <200307271736.05470.bernie@develer.com> (raw)
In-Reply-To: <20030727095158.GE17724@louise.pinerecords.com>
On Sunday 27 July 2003 11:51, Tomas Szepe wrote:
> > [bernie@develer.com]
> >
> > +config IOSCHED_AS
> > + bool "Anticipatory I/O scheduler" if EMBEDDED
> > + default y
> > +
> > +config IOSCHED_DEADLINE
> > + bool "Deadline I/O scheduler" if EMBEDDED
> > + default y
>
> Please provide the help entries too.
I wanted to, and I looked for something in the documentation to
cut & paste instead of making up an inaccurate description myself.
Unfortunately, the documentation wrote by Jens got lost in -mm.
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html
prev parent reply other threads:[~2003-07-27 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 1:19 [PATCH] Make I/O schedulers optional Bernardo Innocenti
2003-07-27 9:51 ` Tomas Szepe
2003-07-27 15:36 ` Bernardo Innocenti [this message]
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=200307271736.05470.bernie@develer.com \
--to=bernie@develer.com \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).