From: Jens Axboe <axboe@suse.de>
To: "Roberts-Thomson, James" <James.Roberts-Thomson@NBNZ.CO.NZ>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug: ll_rw_blk.c, elevator.c and displaying "default" IO Schedule r at boot-time (Cosmetic only)
Date: Wed, 9 Mar 2005 11:30:53 +0100 [thread overview]
Message-ID: <20050309103053.GK28855@suse.de> (raw)
In-Reply-To: <40BC5D4C2DD333449FBDE8AE961E0C330360F8E3@psexc03.nbnz.co.nz>
On Wed, Mar 09 2005, Roberts-Thomson, James wrote:
> Hi,
>
> I've been trying to investigate an IO performance issue on my machine, as
> part of this I've noticed what is (presumably only a cosmetic) issue with
> the messages displayed at kernel boot-time.
>
> In the "good old days" (i.e. older 2.6.x kernel versions), one of the many
> messages displayed at kernel boot-time was "elevator: using XXX as default
> io scheduler", where XXX was one of the IO schedulers (cfq, anticipatory,
> deadline, etc) depending on kernel .config at compile time.
>
> I noticed in 2.6.11, this message has vanished (although this may have
> happened in an earlier kernel), and I now get some messages "io scheduler
> XXX registered". Unfortunately, the "default" scheduler is no longer
> tagged.
Does this work?
--- 2.6.11/drivers/block/elevator.c 2005-01-22 15:22:55.000000000 +1100
+++ test/drivers/block/elevator.c 2005-01-31 22:38:36.000000000 +1100
@@ -180,6 +180,8 @@
__setup("elevator=", elevator_setup);
+static int default_msg = 0;
+
int elevator_init(request_queue_t *q, char *name)
{
struct elevator_type *e = NULL;
@@ -195,6 +197,12 @@
if (!e)
return -EINVAL;
+ if (!default_msg && !strcmp(e->elevator_name, chosen_elevator)) {
+ printk(KERN_INFO "using %s as default io scheduler\n",
+ chosen_elevator);
+ default_msg = 1;
+ }
+
eq = kmalloc(sizeof(struct elevator_queue), GFP_KERNEL);
if (!eq) {
elevator_put(e->elevator_type);
@@ -513,10 +521,7 @@
list_add_tail(&e->list, &elv_list);
spin_unlock_irq(&elv_list_lock);
- printk(KERN_INFO "io scheduler %s registered", e->elevator_name);
- if (!strcmp(e->elevator_name, chosen_elevator))
- printk(" (default)");
- printk("\n");
+ printk(KERN_INFO "io scheduler %s registered\n", e->elevator_name);
return 0;
}
EXPORT_SYMBOL_GPL(elv_register);
--
Jens Axboe
next prev parent reply other threads:[~2005-03-09 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 22:58 Bug: ll_rw_blk.c, elevator.c and displaying "default" IO Schedule r at boot-time (Cosmetic only) Roberts-Thomson, James
2005-03-09 10:30 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 11:27 Srihari Vijayaraghavan
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=20050309103053.GK28855@suse.de \
--to=axboe@suse.de \
--cc=James.Roberts-Thomson@NBNZ.CO.NZ \
--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