From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Chris Mason <mason@suse.com>, Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrea Arcangeli <andrea@suse.de>,
Nick Piggin <piggin@cyberone.com.au>
Subject: Re: Status of the IO scheduler fixes for 2.4
Date: Thu, 3 Jul 2003 14:31:27 +0200 [thread overview]
Message-ID: <200307031431.27153.m.c.p@wolk-project.de> (raw)
In-Reply-To: <1057197726.20903.1011.camel@tiny.suse.com>
On Thursday 03 July 2003 04:02, Chris Mason wrote:
Hi Chris,
> So, the patch attached includes the q->full code but has it off by
> default. I've got code locally for an elvtune interface that can toggle
> q->full check on a per device basis, as well as tune the max io per
> queue. I've got two choices on how to submit it, I can either add a new
> ioctl or abuse the max_bomb_segments field in the existing ioctl.
> If we can agree on the userland tuning side, I can have some kind of
> elvtune patch tomorrow.
what about /proc ?
ciao, Marc
next prev parent reply other threads:[~2003-07-03 12:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 22:26 Marcelo Tosatti
2003-07-02 22:28 ` Marcelo Tosatti
2003-07-03 2:02 ` Chris Mason
2003-07-03 10:58 ` Stephan von Krawczynski
2003-07-03 12:01 ` Chris Mason
2003-07-03 12:07 ` Marc-Christian Petersen
2003-07-03 12:28 ` Stephan von Krawczynski
2003-07-03 12:31 ` Marc-Christian Petersen [this message]
2003-07-03 13:11 ` Chris Mason
2003-07-04 20:01 ` Marcelo Tosatti
2003-07-04 21:37 ` Chris Mason
2003-07-05 0:05 ` Andrea Arcangeli
2003-07-05 0:47 ` Chris Mason
2003-07-05 1:04 ` Andrea Arcangeli
2003-07-06 7:58 ` Marc-Christian Petersen
2003-07-06 18:51 ` Chris Mason
2003-07-07 4:06 ` Nick Piggin
2003-07-05 0:00 ` Andrea Arcangeli
2003-07-05 15:59 ` Marcelo Tosatti
2003-07-05 16:36 ` Andrea Arcangeli
2003-07-03 18:07 ` Chris Mason
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=200307031431.27153.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mason@suse.com \
--cc=piggin@cyberone.com.au \
/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®