public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Roy Franz <roy.lists@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unable to change sata NCQ depth due to readonly /sys/block/sdc/device/queue_depth file
Date: Thu, 28 Jun 2007 17:20:18 -0600	[thread overview]
Message-ID: <46844232.4070409@shaw.ca> (raw)
In-Reply-To: <fa.5pA6aeQb5Qu4sbwkw3l3yzw2bNQ@ifi.uio.no>

Roy Franz wrote:
> Hi,
> 
>  I am unable to change the NCQ settings for a sata drive that
> supports it - NCQ is always on.  This is due to the sysfs queue_depth
> file being read-only.  This is on
> vanilla 2.6.21.5 running with Debian Etch.  (Several earlier versions
> of the kernel
> had this same issue.)  The drive (WD Raptor) is hooked up to a Nvidia
> sata controller.
> 
> amd64:/# ls -al /sys/block/sdc/device/queue_depth
> -r--r--r-- 1 root root 4096 2007-06-28 10:04 
> /sys/block/sdc/device/queue_depth
> amd64:/# cat /sys/block/sdc/device/queue_depth
> 31
> amd64:/#
> 
> I searched but did not find any helpful information on this.  Forcing
> a change by changing permissions on the file did not work.

Looks like sata_nv is missing the change_queue_depth function in the 
SCSI host template, resulting in this file showing as read-only. I'll 
cook up a patch when I get a chance.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-06-28 23:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.5pA6aeQb5Qu4sbwkw3l3yzw2bNQ@ifi.uio.no>
2007-06-28 23:20 ` Robert Hancock [this message]
2007-06-28 17:19 Unable to change sata NCQ depth due to readonly /sys/block/sdc/device/queue_depth file Roy Franz

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=46844232.4070409@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roy.lists@gmail.com \
    /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