public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Gaspar Bakos <gbakos@cfa.harvard.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: elvtune with 2.6 kernels (under FC3)
Date: Mon, 25 Jul 2005 23:16:04 +0200	[thread overview]
Message-ID: <20050725211604.GG3160@stusta.de> (raw)
In-Reply-To: <Pine.SOL.4.58.0507251629130.2429@titan.cfa.harvard.edu>

On Mon, Jul 25, 2005 at 04:31:56PM -0400, Gaspar Bakos wrote:

> Hi,


Hi Gaspar,


> I am cc-ing this to the kernel list, a i have the suspicion that it may
> be a kernel related feature.
> 
> --------------
> I noticed that elvtune does not work on FC3 with a 2.6.12.3
> (self-compiled, pristine) kernel. I also tried it with other 2.6.* kernels.
> 
> elvtune /dev/sde
> ioctl get: Invalid argument
> 
> In fact, I get the same message for all disks, either those on a 3ware
> controller, or SATA disks directly attached to the motherboard.
> The hw is a dual opteron mb with 4Gb RAM.
> 
> Did this command become obsoleted?
> Is there alternativ?


util-linux >= 2.12h gives you a better error message:


# elvtune /dev/hda
ioctl get: Invalid argument

elvtune is only useful on older kernels;
for 2.6 use IO scheduler sysfs tunables instead..
# 


> Cheers
> Gaspar


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-07-25 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 20:31 elvtune with 2.6 kernels (under FC3) Gaspar Bakos
2005-07-25 21:16 ` Adrian Bunk [this message]
2005-07-26 13:15 ` Bill Davidsen

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=20050725211604.GG3160@stusta.de \
    --to=bunk@stusta.de \
    --cc=gbakos@cfa.harvard.edu \
    --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