On Thu, May 31, 2007 at 06:43:46PM -0400, Mark Lord wrote:
> Jeff Garzik wrote:
> >Mark Lord wrote:
> >>Some cards may perform better when their "memory" interface is used
> >>instead of the "I/O" interface, or vice-versa. I'm not sure which
> >>of the two methods was selected by libata (probably
On Thu, May 31, 2007 at 06:43:46PM -0400, Mark Lord wrote:
Jeff Garzik wrote:
Mark Lord wrote:
Some cards may perform better when their memory interface is used
instead of the I/O interface, or vice-versa. I'm not sure which
of the two methods was selected by libata (probably the memory
Jeff Garzik wrote:
Mark Lord wrote:
To maximize throughput, some kind of host-queuing would be needed,
or just have the driver sit in a tight loop, starting the next I/O
immediately when the previous one finishes. Linux isn't that quick
(yet).
I was talking on IRC with Tejun just recently.
Hi Mark,
On 31/05/07, Mark Lord <[EMAIL PROTECTED]> wrote:
Daniel J Blueman wrote:
> On 31/05/07, Mark Lord <[EMAIL PROTECTED]> wrote:
>> Daniel J Blueman wrote:
>> > Whoops, yes. Here is the expected data:
> [snip]
>>
>> Thanks. I'll use that data to update/validate future versions of hdparm.
Mark Lord wrote:
To maximize throughput, some kind of host-queuing would be needed,
or just have the driver sit in a tight loop, starting the next I/O
immediately when the previous one finishes. Linux isn't that quick (yet).
I was talking on IRC with Tejun just recently. There are several
Jeff Garzik wrote:
Mark Lord wrote:
Some cards may perform better when their "memory" interface is used
instead of the "I/O" interface, or vice-versa. I'm not sure which
of the two methods was selected by libata (probably the "memory"
interface).
I am very CF-ignorant. How does libata
Daniel J Blueman wrote:
On 31/05/07, Mark Lord <[EMAIL PROTECTED]> wrote:
Daniel J Blueman wrote:
...
I don't know too much about the specifics, though, but perhaps the
card is only capable of full speed in PIO6, which requires special
cabling
and is currently unsupported in libata (?).
Mark Lord wrote:
Some cards may perform better when their "memory" interface is used
instead of the "I/O" interface, or vice-versa. I'm not sure which
of the two methods was selected by libata (probably the "memory"
interface).
I am very CF-ignorant. How does libata select a memory or I/O
Daniel J Blueman wrote:
hdparm in the other identify mode does list the UDMA3/4 modes twice
[1], which looks odd.
That got fixed a few revisions ago. Update your copy of hdparm
from the masters on sourceforge.
Cheers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Daniel J Blueman wrote:
On 31/05/07, Mark Lord <[EMAIL PROTECTED]> wrote:
Daniel J Blueman wrote:
> Whoops, yes. Here is the expected data:
[snip]
Thanks. I'll use that data to update/validate future versions of hdparm.
At UDMA66, it *should* be capable of the 40MByte/sec realm of readback
On 31/05/07, Mark Lord <[EMAIL PROTECTED]> wrote:
Daniel J Blueman wrote:
> Whoops, yes. Here is the expected data:
[snip]
Thanks. I'll use that data to update/validate future versions of hdparm.
At UDMA66, it *should* be capable of the 40MByte/sec realm of readback perf,
assuming the card
Daniel J Blueman wrote:
Whoops, yes. Here is the expected data:
# hdparm --Istdout /dev/sdb
/dev/sdb:
848a 1f1c 0010 0240 003f 007a
7e40 2020 2020 3131 3638 3032 4432
3830 374a 3335 0002 0002 0004 4844
5820 342e 3034 5361 6e44 6973 6b20 5344
4346 582d 3430 3936 2020 2020
On 31/05/07, Mark Lord <[EMAIL PROTECTED]> wrote:
Daniel J Blueman wrote:
> Hi Mark,
>
> Thanks for the reply; here is the raw identification data:
>
> # hdparm --Istdout /dev/sdb
>
> /dev/sdb:
[snip]
Ooops.. wrong drive. That's NOT a CF card. Try again?
Whoops, yes. Here is the expected
Daniel J Blueman wrote:
Hi Mark,
Thanks for the reply; here is the raw identification data:
# hdparm --Istdout /dev/sdb
/dev/sdb:
045a 3fff c837 0010 003f
2020 2020 2020 5644 5334 3142
5434 4456 3038 474a 0003 3bf5 0034 5634
344f 4139 3641 4844 5437 3232 3532 3544
Hi Mark,
Thanks for the reply; here is the raw identification data:
# hdparm --Istdout /dev/sdb
/dev/sdb:
045a 3fff c837 0010 003f
2020 2020 2020 5644 5334 3142
5434 4456 3038 474a 0003 3bf5 0034 5634
344f 4139 3641 4844 5437 3232 3532 3544
4c41 3338 3020 2020 2020
On 30/05/07, Lee Revell <[EMAIL PROTECTED]> wrote:
On 5/30/07, Daniel J Blueman <[EMAIL PROTECTED]> 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 do you know it's capable
On 30/05/07, Lee Revell [EMAIL PROTECTED] wrote:
On 5/30/07, Daniel J Blueman [EMAIL PROTECTED] 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 do you know it's capable of
Hi Mark,
Thanks for the reply; here is the raw identification data:
# hdparm --Istdout /dev/sdb
/dev/sdb:
045a 3fff c837 0010 003f
2020 2020 2020 5644 5334 3142
5434 4456 3038 474a 0003 3bf5 0034 5634
344f 4139 3641 4844 5437 3232 3532 3544
4c41 3338 3020 2020 2020
Daniel J Blueman wrote:
Hi Mark,
Thanks for the reply; here is the raw identification data:
# hdparm --Istdout /dev/sdb
/dev/sdb:
045a 3fff c837 0010 003f
2020 2020 2020 5644 5334 3142
5434 4456 3038 474a 0003 3bf5 0034 5634
344f 4139 3641 4844 5437 3232 3532 3544
On 31/05/07, Mark Lord [EMAIL PROTECTED] wrote:
Daniel J Blueman wrote:
Hi Mark,
Thanks for the reply; here is the raw identification data:
# hdparm --Istdout /dev/sdb
/dev/sdb:
[snip]
Ooops.. wrong drive. That's NOT a CF card. Try again?
Whoops, yes. Here is the expected data:
#
Daniel J Blueman wrote:
Whoops, yes. Here is the expected data:
# hdparm --Istdout /dev/sdb
/dev/sdb:
848a 1f1c 0010 0240 003f 007a
7e40 2020 2020 3131 3638 3032 4432
3830 374a 3335 0002 0002 0004 4844
5820 342e 3034 5361 6e44 6973 6b20 5344
4346 582d 3430 3936 2020 2020
On 31/05/07, Mark Lord [EMAIL PROTECTED] wrote:
Daniel J Blueman wrote:
Whoops, yes. Here is the expected data:
[snip]
Thanks. I'll use that data to update/validate future versions of hdparm.
At UDMA66, it *should* be capable of the 40MByte/sec realm of readback perf,
assuming the card
Daniel J Blueman wrote:
On 31/05/07, Mark Lord [EMAIL PROTECTED] wrote:
Daniel J Blueman wrote:
Whoops, yes. Here is the expected data:
[snip]
Thanks. I'll use that data to update/validate future versions of hdparm.
At UDMA66, it *should* be capable of the 40MByte/sec realm of readback
Daniel J Blueman wrote:
hdparm in the other identify mode does list the UDMA3/4 modes twice
[1], which looks odd.
That got fixed a few revisions ago. Update your copy of hdparm
from the masters on sourceforge.
Cheers
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
Mark Lord wrote:
Some cards may perform better when their memory interface is used
instead of the I/O interface, or vice-versa. I'm not sure which
of the two methods was selected by libata (probably the memory
interface).
I am very CF-ignorant. How does libata select a memory or I/O
Daniel J Blueman wrote:
On 31/05/07, Mark Lord [EMAIL PROTECTED] wrote:
Daniel J Blueman wrote:
...
I don't know too much about the specifics, though, but perhaps the
card is only capable of full speed in PIO6, which requires special
cabling
and is currently unsupported in libata (?).
Jeff Garzik wrote:
Mark Lord wrote:
Some cards may perform better when their memory interface is used
instead of the I/O interface, or vice-versa. I'm not sure which
of the two methods was selected by libata (probably the memory
interface).
I am very CF-ignorant. How does libata select a
Mark Lord wrote:
To maximize throughput, some kind of host-queuing would be needed,
or just have the driver sit in a tight loop, starting the next I/O
immediately when the previous one finishes. Linux isn't that quick (yet).
I was talking on IRC with Tejun just recently. There are several
Hi Mark,
On 31/05/07, Mark Lord [EMAIL PROTECTED] wrote:
Daniel J Blueman wrote:
On 31/05/07, Mark Lord [EMAIL PROTECTED] wrote:
Daniel J Blueman wrote:
Whoops, yes. Here is the expected data:
[snip]
Thanks. I'll use that data to update/validate future versions of hdparm.
At UDMA66, it
Jeff Garzik wrote:
Mark Lord wrote:
To maximize throughput, some kind of host-queuing would be needed,
or just have the driver sit in a tight loop, starting the next I/O
immediately when the previous one finishes. Linux isn't that quick
(yet).
I was talking on IRC with Tejun just recently.
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
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],
On 5/30/07, Daniel J Blueman <[EMAIL PROTECTED]> 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 do you know it's capable of 40MB/s read?
Lee
-
To unsubscribe from this list:
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
no
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
no
On 5/30/07, Daniel J Blueman [EMAIL PROTECTED] 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 do you know it's capable of 40MB/s read?
Lee
-
To unsubscribe from this list: send
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],
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
38 matches
Mail list logo
