From: Jeff Garzik <jgarzik@pobox.com>
To: Albert Lee <albertcc@tw.ibm.com>, Jens Axboe <axboe@suse.de>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: IDE Linux <linux-ide@vger.kernel.org>, Doug Maxey <dwm@maxeymade.com>
Subject: Re: [PATCH] libata: Use ATAPI PIO mode for specific request buffer sizes
Date: Thu, 02 Dec 2004 06:21:08 -0500 [thread overview]
Message-ID: <41AEFAA4.80907@pobox.com> (raw)
In-Reply-To: <00ce01c4d6b8$d222d080$bc604109@tw.ibm.com>
Albert Lee wrote:
> Hi, Jeff:
>
> After some testing, it seems that some PATA host adapter (ex. pdc20275) cannot
> work reliably with specific request buffer sizes under ATAPI DMA mode.
>
> Detailed test result:
> 4096, 2048, 1024, 512, 256: OK
> 384, 257, 255, 128, 96, 64, 32: failed (irq lost)
>
> It seems multiple of 256 bytes are the safe ATAPI DMA buffer sizes to use.
>
> Attached please find the patch against libata-dev-2.6 for your review.
> Two changes:
> 1. Use ATAPI PIO mode for ATAPI REQUEST_SENSE
> 2. Use ATAPI PIO mode for specific SCSI commands issued to ATAPI device that
> buffer_size % 256 != 0.
>
> Since for most commands, buffer_size % 256 is 0, this patch
> won't introduce big impact to the performance of libata (hopefully).
>
> Tested OK on on my machine with pdc20275 and ASUS CD-RW drive.
hmmmmmmm.
Your change #1 makes perfect sense, and I agree it is the safer (and
more simple) route.
I must ponder change #2 some more (after some sleep :)). In particular,
I am concerned that making change #2 across all controllers will hurt
performance on the commands whose data length is not purely sector-sized
chunks.
Would you mind splitting up change #1 and #2 into separate patches?
Jeff
next prev parent reply other threads:[~2004-12-02 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 8:44 [PATCH] libata: Use ATAPI PIO mode for specific request buffer sizes Albert Lee
2004-12-02 11:21 ` Jeff Garzik [this message]
2004-12-03 7:18 ` Albert Lee
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=41AEFAA4.80907@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=albertcc@tw.ibm.com \
--cc=axboe@suse.de \
--cc=dwm@maxeymade.com \
--cc=linux-ide@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 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.