linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Tejun Heo <htejun@gmail.com>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Mingming Cao <cmm@us.ibm.com>
Subject: Re: Fall back io scheduler for 2.6.15?
Date: Sat, 21 Jan 2006 12:44:08 +0100	[thread overview]
Message-ID: <20060121114408.GS13429@suse.de> (raw)
In-Reply-To: <43D1D134.5070401@gmail.com>

On Sat, Jan 21 2006, Tejun Heo wrote:
> Jens Axboe wrote:
> >On Sat, Jan 14 2006, Chuck Ebbert wrote:
> >
> >>In-Reply-To: <20060113174914.7907bf2c.akpm@osdl.org>
> >>
> >>On Fri, 13 Jan 2006, Andrew Morton wrote:
> >>
> >>
> >>>OK.  And I assume that AS wasn't compiled, so that's why it fell back?
> >>
> >>As of 2.6.15 you need to use "anticipatory" instead of "as".
> >>
> >>Maybe this patch would help?
> >>
> >>Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com>
> >>
> >>--- 2.6.15a.orig/block/elevator.c
> >>+++ 2.6.15a/block/elevator.c
> >>@@ -150,6 +150,13 @@ static void elevator_setup_default(void)
> >>	if (!chosen_elevator[0])
> >>		strcpy(chosen_elevator, CONFIG_DEFAULT_IOSCHED);
> >>
> >>+	/*
> >>+	 * Be backwards-compatible with previous kernels, so users
> >>+	 * won't get the wrong elevator.
> >>+	 */
> >>+	if (!strcmp(chosen_elevator, "as"))
> >>+		strcpy(chosen_elevator, "anticipatory");
> >>+
> >> 	/*
> >> 	 * If the given scheduler is not available, fall back to no-op.
> >> 	 */
> >
> >
> >We probably should apply this, since it used to be 'as'.
> >
> 
> Just out of curiousity, why did 'as' get renamed to 'anticipatory'?

Side effect really, not intentional. 'as' always registered itself with
the elevator core as "anticipatory", the logic to match elevator=foo
string to scheduler used to be completely seperate prior to the addition
of online switchable elevators. So when those two were tied together,
the "as" disappeared. I guess the right thing to do at that time was to
rename "anticipatory", but that didn't happen...

-- 
Jens Axboe


  reply	other threads:[~2006-01-21 11:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-14 16:10 Fall back io scheduler for 2.6.15? Chuck Ebbert
2006-01-16  8:43 ` Jens Axboe
2006-01-19 19:38   ` Nate Diller
2006-01-21  6:14   ` Tejun Heo
2006-01-21 11:44     ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-05  3:51 ext3 allocate-with-reservation latencies Lee Revell
2005-04-07 13:08 ` Stephen C. Tweedie
2005-04-07 23:37   ` Mingming Cao
2005-04-08 14:40     ` Stephen C. Tweedie
2005-04-08 18:10       ` Mingming Cao
2005-04-11 11:48         ` Stephen C. Tweedie
2005-04-11 18:38           ` Mingming Cao
2005-04-11 19:57             ` Stephen C. Tweedie
2005-04-12  6:41               ` Mingming Cao
2005-04-12 11:18                 ` Stephen C. Tweedie
2005-04-12 23:27                   ` Mingming Cao
2005-04-13 10:29                     ` Stephen C. Tweedie
2005-04-22 22:10                       ` [RFC][PATCH] Reduce ext3 allocate-with-reservation lock latencies Mingming Cao
2005-04-28  3:45                         ` Lee Revell
2005-04-28 19:14                           ` [RFC] Adding multiple block allocation to current ext3 Mingming Cao
2006-01-10 23:26                             ` [PATCH 0/5] " Mingming Cao
2006-01-11  5:25                               ` Andrew Morton
2006-01-11 19:17                                 ` Mingming Cao
2006-01-11 19:43                                   ` Andrew Morton
2006-01-14  1:12                                     ` Fall back io scheduler for 2.6.15? Mingming Cao
2006-01-14  1:49                                       ` Andrew Morton
2006-01-14  5:22                                         ` Dave Jones
2006-01-16  8:43                                         ` Jens Axboe
2006-01-19 19:37                                           ` Nate Diller
2006-01-20  8:10                                             ` 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=20060121114408.GS13429@suse.de \
    --to=axboe@suse.de \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=cmm@us.ibm.com \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@vger.kernel.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).