All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Johann-Christoph Jacob <johann-christoph.jacob@fhtw-berlin.de>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_sil24 not configuring drive right?
Date: Thu, 21 Feb 2008 10:23:51 +0900	[thread overview]
Message-ID: <47BCD2A7.1030504@gmail.com> (raw)
In-Reply-To: <47BC7D47.9060608@fhtw-berlin.de>

Johann-Christoph Jacob wrote:
> my problem is not with the transfer mode but with the NCQ queue_depth.
> My bootlog shows:
> ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 1)
> but i would like it to show:
> ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
> or something similar.
> I was not exact enough concerning the writeability of
> /sys/block/sda/device/queue_depth
> The file is not read only but writing to it fails:
> echo 31 > /sys/block/sda/device/queue_depth
> bash: echo: write error: Invalid argument

Right.

>>> ATA device, with non-removable media
>>>         Model Number:       WDC WD1200BEVS-07LAT0                   
>>>         Serial Number:      WD-WXE906801963
>>>         Firmware Revision:  01.06M01
>>> Standards:
>>>         Supported: 7 6 5 4 
>>>         Likely used: 7
>>> Configuration:
>>>         Logical         max     current
>>>         cylinders       16383   16383
>>>         heads           16      16
>>>         sectors/track   63      63
>>>         --
>>>         CHS current addressable sectors:   16514064
>>>         LBA    user addressable sectors:  234441648
>>>         LBA48  user addressable sectors:  234441648
>>>         device size with M = 1024*1024:      114473 MBytes
>>>         device size with M = 1000*1000:      120034 MBytes (120 GB)
>>> Capabilities:
>>>         LBA, IORDY(can be disabled)
>>>         Queue depth: 1

Hmm... Here it is.  Interesting.  The drive is reporting queue depth of
1.  Interesting.  This is the first time I see this.  The drive is
telling libata that it supports NCQ and the max queue depth is 1 and
libata configures it accordingly.  I'll ask wd about it.

Thanks.

-- 
tejun

  reply	other threads:[~2008-02-21  1:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47BB8346.4070400@fhtw-berlin.de>
     [not found] ` <47BBA66C.7050900@gmail.com>
2008-02-20 19:19   ` sata_sil24 not configuring drive right? Johann-Christoph Jacob
2008-02-21  1:23     ` Tejun Heo [this message]
2008-02-21  6:53       ` Tejun Heo
2008-02-21 12:26         ` Johann-Christoph Jacob
2008-02-20 19:16 Johann-Christoph Jacob
  -- strict thread matches above, loose matches on Subject: below --
2007-06-19  4:28 Theo Baumgartner
2007-07-03  6:38 ` Tejun Heo

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=47BCD2A7.1030504@gmail.com \
    --to=htejun@gmail.com \
    --cc=johann-christoph.jacob@fhtw-berlin.de \
    --cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.