mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nate Diller <nate.diller@gmail.com>
To: Jens Axboe <axboe@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	cmm@us.ibm.com, seelam@cs.utep.edu, linux-kernel@vger.kernel.org,
	ext2-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2][RESEND] Default iosched fixes (was: Fall back io scheduler for 2.6.15?)
Date: Mon, 23 Jan 2006 11:50:41 -0800	[thread overview]
Message-ID: <5c49b0ed0601231150i39e678f3s9dd99c308ffb5157@mail.gmail.com> (raw)
In-Reply-To: <20060121114841.GT13429@suse.de>

On 1/21/06, Jens Axboe <axboe@suse.de> wrote:
> On Fri, Jan 20 2006, Nate Diller wrote:
> > My previous default iosched patch did a poor job dealing with the
> > 'elevator=' boot-time option.  The old behavior falls back to the
> > compiled-in default if the requested one is not registered at boot
> > time.  This patch dynamically evaluates which default
> > to use, and emits a suitable error message when the requested scheduler
> > is not available.  It also does the 'as' -> 'anticipatory' conversion
> > before elevator registration, which along with a modified registration
> > function, allows it to correctly indicate which default scheduler is
> > in use.
>
> I'm a little confused by your description - what problem does this patch
> actually solve? We already fall back to the default, and we already do
> the "as" conversion. It does seem to cleanup the code, just curious
> since your description seems to promise a little more than what it
> actually adds.

It makes the ' (default)' printk that happens at elevator registration
time behave (more) correctly.  My original patch rather ignored that
segment of code.  The current behavior is to only print ' (default)'
when one was specified at boot time, and not if 'as' was requested
either, since it doesn't understand the 'as -> anticipatory'
conversion.  Now, it will display correctly the one selected at
compile-time, if none was specified at boot, and when the boot-time
option was 'as'.

It also handles modular defaults better; although they cannot be
specified in kconfig, a default requested at boot-time will now still
work, even if it's a module.  When the boot-time requested scheduler
is not loaded, it will fall back to the compiled-in default; when it
is, it gets used.

NATE

  reply	other threads:[~2006-01-23 19:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20  0:04 [PATCH] " Nate Diller
2006-01-20  8:11 ` Jens Axboe
2006-01-20 23:17   ` [PATCH 1/2][RESEND] " Nate Diller
2006-01-20 23:24     ` [PATCH 2/2][RESEND] " Nate Diller
2006-01-21 11:40       ` Jens Axboe
2006-01-21 11:48     ` [PATCH 1/2][RESEND] " Jens Axboe
2006-01-23 19:50       ` Nate Diller [this message]
2006-01-23 21:02         ` 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=5c49b0ed0601231150i39e678f3s9dd99c308ffb5157@mail.gmail.com \
    --to=nate.diller@gmail.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=cmm@us.ibm.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seelam@cs.utep.edu \
    /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®