Prev: improve the performance of large sequential write NFS workloads
Next: a perf and some sched patches
From: Romain Kubany on 17 Dec 2009 07:10
Here it is under the 2.6.28 :

# hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media
Model Number: Virtual HD
Serial Number:
Firmware Revision: 1.1.0
Standards:
Likely used: 2
Configuration:
Logical max current
cylinders 16383 65535
heads 16 16
sectors/track 63 255
--
bytes/track: 65024 bytes/sector: 512
CHS current addressable sectors: 267382800
LBA user addressable sectors: 267382800
device size with M = 1024*1024: 130558 MBytes
device size with M = 1000*1000: 136899 MBytes (136 GB)
Capabilities:
LBA, IORDY(can be disabled)
Buffer size: 64.0kB
Standby timer values: spec'd by Vendor
R/W multiple sector transfer: Max = 128 Current = 128
DMA: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=333ns IORDY flow control=120ns


-----Message d'origine-----
De�: Jeff Garzik [mailto:jgpobox(a)gmail.com] De la part de Jeff Garzik
Envoy�: jeudi 17 d�cembre 2009 13:06
��: Romain Kubany
Cc�: Mikael Pettersson; linux-kernel(a)vger.kernel.org; linux-ide(a)vger.kernel.org
Objet�: Re: Possible regression of LBA48 support for piix

On 12/17/2009 06:03 AM, Jeff Garzik wrote:
> On 12/17/2009 05:04 AM, Romain Kubany wrote:
>> Here is the new kernel config file : http://pastebin.com/f65fd472b
>
> I would definitely be interested in seeing the 'dmesg' output for
> libata, and results from a more recent kernel.

Also, what does 'hdparm -I /dev/XXXX' output look like?

Jeff




--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jeff Garzik on 17 Dec 2009 07:10
On 12/17/2009 06:03 AM, Jeff Garzik wrote:
> On 12/17/2009 05:04 AM, Romain Kubany wrote:
>> Here is the new kernel config file : http://pastebin.com/f65fd472b
>
> I would definitely be interested in seeing the 'dmesg' output for
> libata, and results from a more recent kernel.

Also, what does 'hdparm -I /dev/XXXX' output look like?

Jeff



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jeff Garzik on 17 Dec 2009 07:10
On 12/17/2009 06:34 AM, Romain Kubany wrote:
> Thanks for your concern. :)
>
> Here is the full dmesg output : http://pastebin.com/f484004a5 (2.6.28 with same config as in my previous mail)
>
> I'm going to test a 2.6.32.1 kernel and similar config

[ 0.804002] ata1.00: ATA-0: Virtual HD, 1.1.0, max MWDMA2
[ 0.804002] ata1.00: 267382800 sectors, multi 128: LBA

For starters, the virtual disk is reporting ATA version 0. That means
the disk is telling us it does not support LBA48 or other advanced
features. libata (and probably IDE, too) happily obliges.

That sounds like either a broken emulation, or some information returned
from the virtual disk got zeroed somehow.

Jeff


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jeff Garzik on 17 Dec 2009 07:30
On 12/17/2009 07:07 AM, Romain Kubany wrote:
> Here it is under the 2.6.28 :
>
> # hdparm -I /dev/sda
>
> /dev/sda:
>
> ATA device, with non-removable media
> Model Number: Virtual HD
> Serial Number:
> Firmware Revision: 1.1.0
> Standards:
> Likely used: 2
> Configuration:
> Logical max current
> cylinders 16383 65535
> heads 16 16
> sectors/track 63 255
> --
> bytes/track: 65024 bytes/sector: 512
> CHS current addressable sectors: 267382800
> LBA user addressable sectors: 267382800
> device size with M = 1024*1024: 130558 MBytes
> device size with M = 1000*1000: 136899 MBytes (136 GB)

Yeah, that info is straight from the virtual disk, without any sort of
massaging. The disk is reporting 136GB max, so I would poke around
Windows to see if a setting changed somewhere... maybe there is an "old
IDE compatible" setting that got turned on, for the virtual hd?

Jeff



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Bartlomiej Zolnierkiewicz on 17 Dec 2009 08:40
On Thursday 17 December 2009 01:22:22 pm Jeff Garzik wrote:
> On 12/17/2009 07:07 AM, Romain Kubany wrote:
> > Here it is under the 2.6.28 :
> >
> > # hdparm -I /dev/sda
> >
> > /dev/sda:
> >
> > ATA device, with non-removable media
> > Model Number: Virtual HD
> > Serial Number:
> > Firmware Revision: 1.1.0
> > Standards:
> > Likely used: 2
> > Configuration:
> > Logical max current
> > cylinders 16383 65535
> > heads 16 16
> > sectors/track 63 255
> > --
> > bytes/track: 65024 bytes/sector: 512
> > CHS current addressable sectors: 267382800
> > LBA user addressable sectors: 267382800
> > device size with M = 1024*1024: 130558 MBytes
> > device size with M = 1000*1000: 136899 MBytes (136 GB)
>
> Yeah, that info is straight from the virtual disk, without any sort of
> massaging. The disk is reporting 136GB max, so I would poke around
> Windows to see if a setting changed somewhere... maybe there is an "old
> IDE compatible" setting that got turned on, for the virtual hd?

It is also possible that this virtual disk has never worked with ata_piix
driver and worked with piix driver in the older kernels because of pure luck.

In 2.6.28 I've fixed LBA48 checks in IDE to match libata (see commit 942dcd8
for details) so it would be worth to try:

- simulating the older buggy IDE behavior with 2.6.32 kernel

or

- staring long enough at 'hdparm --Istdout /dev/sda' output

first.

--
Bartlomiej Zolnierkiewicz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: improve the performance of large sequential write NFS workloads
Next: a perf and some sched patches