public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Dave Jones <davej@suse.de>
Cc: Brian Ristuccia <bristucc@sw.starentnetworks.com>,
	linux-kernel@vger.kernel.org
Subject: Re: elvtune fails with DAC960 and devfs on 2.4.14
Date: Wed, 14 Nov 2001 08:56:42 +0100	[thread overview]
Message-ID: <20011114085642.G17933@suse.de> (raw)
In-Reply-To: <20011113145315.T22467@osiris.978.org> <Pine.LNX.4.30.0111132206431.6089-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.30.0111132206431.6089-100000@Appserv.suse.de>

On Tue, Nov 13 2001, Dave Jones wrote:
> On Tue, 13 Nov 2001, Brian Ristuccia wrote:
> 
> > I can't seem to adjust the elevator parameters for this block device, but
> > can't:
> > # elvtune /dev/rd/disc0/disc
> > ioctl get: Invalid argument
> 
> DAC960.c doesn't know about BLKELVSET / BLKELVGET, and control is
> only passed down to the generic ioctl in the case of BLKBSZSET,
> and doesn't have a default: entry in the switch statement of
> DAC960_IOCTL()
> 
> I've not seen one of these devices, so I'm not sure if this makes
> sense or not, but passing on requests to the lower level should
> be a simple..
> 
> 	default:
> 		return( blk_ioctl(Inode->i_rdev, Request, Argument));
> 
> Addition.

Or just add it to the BLKBSZGET etc string that pass it on to blk_ioctl
anyways.

> There may be other reasons this driver doesn't provide the
> elevator ioctls though.

None, it was simply never added.

-- 
Jens Axboe


      reply	other threads:[~2001-11-14  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 19:53 elvtune fails with DAC960 and devfs on 2.4.14 Brian Ristuccia
2001-11-13 21:11 ` Dave Jones
2001-11-14  7:56   ` Jens Axboe [this message]

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=20011114085642.G17933@suse.de \
    --to=axboe@suse.de \
    --cc=bristucc@sw.starentnetworks.com \
    --cc=davej@suse.de \
    --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