All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Nate Diller <nate.diller@gmail.com>
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] Default iosched fixes (was: Fall back io scheduler for 2.6.15?)
Date: Fri, 20 Jan 2006 09:11:45 +0100	[thread overview]
Message-ID: <20060120081145.GD4213@suse.de> (raw)
In-Reply-To: <5c49b0ed0601191604p4fa53404r783b3a703e922b13@mail.gmail.com>

On Thu, Jan 19 2006, Nate Diller wrote:
> My previous default iosched patch did a poor job dealing with the
> 'elevator=' boot-time option.  Jens' recent solution would fail if the
> selected default were compiled as a module, and I find that scenario
> useful for debugging.  This patch dynamically evaluates which default
> to use, and emits suitable error messages when the requested scheduler
> is not available.  It also indicates the compiled-in default scheduler
> at registration time, and includes a version of Chuck Ebbert's 'as' ->
> 'anticipatory' compatability patch.
> 
> Tested for a range of boot options on 2.6.13-rc5-mm1, should apply to
> any recent kernel.

Your patch doesn't apply at all, the file has even been moved. Please
test a 2.6.15 or newer kernel and you'll find that the problem you
envision doesn't exist.

-- 
Jens Axboe


  reply	other threads:[~2006-01-20  8:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20  0:04 [PATCH] Default iosched fixes (was: Fall back io scheduler for 2.6.15?) Nate Diller
2006-01-20  8:11 ` Jens Axboe [this message]
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
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=20060120081145.GD4213@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@osdl.org \
    --cc=cmm@us.ibm.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nate.diller@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.