From: Jeff Garzik <jgarzik@pobox.com>
To: Jan Marek <linux@hazard.jcu.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9: VIA sATA cannot switch to 32bit I/O?
Date: Tue, 21 Dec 2004 14:32:16 -0500 [thread overview]
Message-ID: <41C87A40.40308@pobox.com> (raw)
In-Reply-To: <20041221144119.GA21507@hazard.jcu.cz>
Jan Marek wrote:
> Hallo l-k,
>
> I have problem with my Abit AV8 MB (s939 with VIA KT800Pro chipset and
> VIA sATA controller and 120GB Seagate Barracuda disk): I cannot switch
> 32bit access to disk to on?! I'm using libata driver...
>
> When I use hdparm -c1 /dev/sda, I've got some error message (sorry, I
> haven't this message here, it's my home computer). Therefore disk is too
> slow to putting data for burning CD's and I need 'burnfree' feature...
>
> Please, have anyone advice for me to speedup disk access, or is it
> possible?
This will not speed up disk access. libata uses 16-bit I/O
unconditionally for PIO data transfers...
...but you are using DMA for data transfers, which is light years
faster than PIO anyway.
Jeff
prev parent reply other threads:[~2004-12-21 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 14:41 2.6.9: VIA sATA cannot switch to 32bit I/O? Jan Marek
2004-12-21 19:32 ` Jeff Garzik [this message]
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=41C87A40.40308@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@hazard.jcu.cz \
/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.