linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: linux-ide@vger.kernel.org,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jeff@garzik.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Compact Flash performance...
Date: Thu, 31 May 2007 00:56:56 +0200	[thread overview]
Message-ID: <200705310056.56449.bzolnier@gmail.com> (raw)
In-Reply-To: <6278d2220705301510y2d81f69eu38fb778d32de05e1@mail.gmail.com>


Hi,

Since you are using libata ata_piix driver and not IDE piix one
Jeff and/or Alan are the right people to ask this question...

Anyway...

On Thursday 31 May 2007, Daniel J Blueman wrote:
> I have a SanDisk Extreme IV 4GB CF card, capable of 40MB/s read, but
> am seeing 30MB/s read [1], connected directly to the IDE bus on my
> ICH8 controller.
> 
> How can I find out if this would be a timing or configuration issue?
> On 2.6.20.5 [2], the 120nS timing looks to be right [3], but perhaps

multi-word DMA cycle timing seems to be configured OK

Shouldn't really matter since it is for multi-word DMA transfers
and this device is using UDMA transfers.

> no multi-word transfer is hurting here...alas, it can't be enabled
> with the libata subsystem and 'hdparm -m', so what else?

-m is for multi sector PIO transfers and probably won't help here

Everything (except harmless "abnormal status" garbage) seems fine.

Where does the max 40MB/s come from?  Were you able to get this device to
work with this speed using some other controller and/or other OS-es?

Thanks,
Bart

> Daniel
> 
> --- [1]
> 
> # hdparm -t /dev/sdb
> /dev/sdb:
>  Timing buffered disk reads:   94 MB in  3.05 seconds =  30.79 MB/sec
> 
> --- [2]
> 
> ata7: PATA max UDMA/100 cmd 0x000000000001bc00 ctl 0x000000000001b882
> bmdma 0x000000000001b400 irq 17
> ata7.00: CFA: SanDisk SDCFX-4096, HDX 4.04, max UDMA/66
> ata7.00: 8027712 sectors, multi 0: LBA
> ata7.00: configured for UDMA/66
> ATA: abnormal status 0x7F on port 0x000000000001b807
> scsi 6:0:0:0: Direct-Access     ATA      SanDisk SDCFX-40 HDX  PQ: 0 ANSI: 5
> SCSI device sdb: 8027712 512-byte hdwr sectors (4110 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: write cache: disabled, read cache: enabled, doesn't
> support DPO or FUA
> SCSI device sdb: 8027712 512-byte hdwr sectors (4110 MB)
> sdb: sdb1
> sd 6:0:0:0: Attached scsi removable disk sdb
> 
> --- [3]
> 
> # hdparm -I /dev/sdb
> 
> /dev/sdb:
> 
> CompactFlash ATA device, with removable media
>         Model Number:       SanDisk SDCFX-4096
>         Serial Number:      116802D2807J3335
>         Firmware Revision:  HDX 4.04
> Standards:
>         Supported: 4
>         Likely used: 4
> Configuration:
>         Logical         max     current
>         cylinders       7964    7964
>         heads           16      16
>         sectors/track   63      63
>         --
>         CHS current addressable sectors:    8027712
>         LBA    user addressable sectors:    8027712
>         device size with M = 1024*1024:        3919 MBytes
>         device size with M = 1000*1000:        4110 MBytes (4 GB)
> Capabilities:
>         LBA, IORDY(may be)(cannot be disabled)
>         Standby timer values: spec'd by Vendor
>         R/W multiple sector transfer: Max = 4   Current = 0
>         DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
>              Cycle time: min=120ns recommended=120ns
>         PIO: pio0 pio1 pio2 pio3 pio4
>              Cycle time: no flow control=120ns  IORDY flow control=120ns
> Commands/features:
>         Enabled Supported:
>                 Write cache
>            *    CFA feature set
> -- 
> Daniel J Blueman

  parent reply	other threads:[~2007-05-30 22:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 22:10 Compact Flash performance Daniel J Blueman
2007-05-30 22:31 ` Lee Revell
2007-05-31  9:18   ` Daniel J Blueman
2007-05-30 22:56 ` Bartlomiej Zolnierkiewicz [this message]
2007-05-31  3:24 ` Mark Lord
2007-05-31  9:22   ` Daniel J Blueman
2007-05-31 12:22     ` Mark Lord
2007-05-31 17:25       ` Daniel J Blueman
2007-05-31 20:54         ` Mark Lord
2007-05-31 21:39           ` Daniel J Blueman
2007-05-31 22:33             ` Mark Lord
2007-05-31 22:35               ` Mark Lord
2007-05-31 22:37               ` Jeff Garzik
2007-05-31 22:43                 ` Mark Lord
2007-06-02  5:10                   ` Willy Tarreau
2007-05-31 23:47               ` Daniel J Blueman
2007-05-31 22:40             ` Mark Lord
2007-05-31 23:26               ` Jeff Garzik
     [not found] <fa.XmtWMJk5gwBC00HJh+5O62Vx8eA@ifi.uio.no>
     [not found] ` <fa.fl4+oXGwE5VC39h2DLdFoBUbqV4@ifi.uio.no>
     [not found]   ` <fa.+cW0LouEqSiZ6zrmBDeBJxRjPTg@ifi.uio.no>
     [not found]     ` <fa.PM7erd/Gm1gq8ZshwTBJwux7o6o@ifi.uio.no>
     [not found]       ` <fa.MYVClL+Q9g/jFTcUNWOeysiV0Ig@ifi.uio.no>
     [not found]         ` <fa.Q4zXu+xtMAT5H5vbl/zgxZk/Ivo@ifi.uio.no>
2007-06-01  0:00           ` Robert Hancock

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=200705310056.56449.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=daniel.blueman@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).