From: Oliver Janscheidt <oliver.janscheidt@rub.de>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Problems with disc-performance and libata
Date: Mon, 27 Aug 2007 08:44:00 +0200 [thread overview]
Message-ID: <1188197040.6622.21.camel@WG4> (raw)
In-Reply-To: <6bffcb0e0708261659y15b344b7h783a1f5ea43a3899@mail.gmail.com>
Hi Michal,
thanks for your reply!
Am Montag, den 27.08.2007, 01:59 +0200 schrieb Michal Piotrowski:
> Hi Oliver,
>
> [Adding linux-ide to CC]
>
> On 26/08/07, Oliver Janscheidt <oliver.janscheidt@rub.de> wrote:
> > Hi,
> >
> > I'm using a Lenovo Thinkpad with TOSHIBA MK1234GS HD and MATSHITA
> > DVD-RAM UJ-850 on 82801GBM/GHM (ICH7 Family) Serial ATA Storage
> > Controller IDE. The Kernel is a 2.6.22.1 from Kernel.org (with 2.6.23-rc1-
> > and hdaps-queue-freezing-patch).
>
> Could you try 2.6.23-rc3-git10?
As soon as possible I'll compile the 2.6.23-rc3-git10 source code and
give a feedback at this point. Could the problem have to do with the
queue freezing patch?
>
> >
> > sudo hdparm -t /dev/scd0 gives
> >
> > Timing buffered disk reads: 2 MB in 4.47 seconds = 457.75 kB/sec
>
> Are you using cracked cd/dvd?
>
>
> cracked dvd
>
> /sbin/hdparm -t /dev/scd0
>
> /dev/scd0:
> Timing buffered disk reads: 2 MB in 6.36 seconds = 321.78 kB/sec
>
>
> new shiny dvd
>
> /sbin/hdparm -t /dev/scd0
>
> /dev/scd0:
> Timing buffered disk reads: 14 MB in 3.14 seconds = 4.46 MB/sec
Obviously it makes no difference weather the disc is new or old
(original or cracked). For my first post I used an original film-dvd.
But I repeated it with copy (DVD+R) and got the same results about 400
kB/sec.
>
> >
> > sudo hdparm -t /dev/sda gives
> >
> > Timing buffered disk reads: 102 MB in 3.04 seconds = 33.51 MB/sec
>
> I've got an old Maxtor HDD (also 5,400 rpm) results are similar.
So maybe the problem only affects /dev/scd0? Possibly the driver can't
deal with the IBM Ultrabay (swapping drives "on the fly")?
> >
> > which is a quite poor performance and makes any streaming impossible.
> > Obviously UDMA is working correctly as dmesg | grep UDMA says:
> >
> > [ 43.636590] ata1: SATA max UDMA/133 cmd 0xffffc20004612500 ctl
> > 0x0000000000000000 bmdma 0x0000000000000000 irq 314
> > [ 43.636595] ata2: SATA max UDMA/133 cmd 0xffffc20004612580 ctl
> > 0x0000000000000000 bmdma 0x0000000000000000 irq 314
> > [ 43.636599] ata3: SATA max UDMA/133 cmd 0xffffc20004612600 ctl
> > 0x0000000000000000 bmdma 0x0000000000000000 irq 314
> > [ 43.636603] ata4: SATA max UDMA/133 cmd 0xffffc20004612680 ctl
> > 0x0000000000000000 bmdma 0x0000000000000000 irq 314
> > [ 44.177980] ata1.00: ATA-7: TOSHIBA MK1234GSX, AH002E, max UDMA/100
> > [ 44.179192] ata1.00: configured for UDMA/100
> > [ 44.326918] ata5: PATA max UDMA/133 cmd 0x00000000000101f0 ctl
> > 0x00000000000103f6 bmdma 0x0000000000011880 irq 14
> > [ 44.326922] ata6: PATA max UDMA/133 cmd 0x0000000000010170 ctl
> > 0x0000000000010376 bmdma 0x0000000000011888 irq 15
> > [ 44.571970] ata5.00: ATAPI: MATSHITADVD-RAM UJ-850, RB01, max UDMA/33
> > [ 44.738552] ata5.00: configured for UDMA/33
> > [ 0.610332] ata5.00: configured for UDMA/33
> > [ 0.750296] ata1.00: configured for UDMA/100
> >
> > Is there any solution for that problem or at least a workaround?
> >
> > I also tried to recompile the kernel as recommended in the official
> > libata-faq ( http://linux-ata.org/faq.html ) but the system stuck when
> > booting the root-partition. Booting with combined_mode=libata or
> > combined_mode=ide didn't affect the performance, too.
> >
> > Thanks in advance,
> >
> > Oli
> >
>
> Regards,
> Michal
>
Thanks,
Oli
next prev parent reply other threads:[~2007-08-27 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 20:08 Problems with disc-performance and libata Oliver Janscheidt
2007-08-26 23:59 ` Michal Piotrowski
2007-08-27 6:44 ` Oliver Janscheidt [this message]
2007-08-28 6:44 ` Oliver Janscheidt
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=1188197040.6622.21.camel@WG4 \
--to=oliver.janscheidt@rub.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@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