public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Jens Axboe <axboe@suse.de>
Cc: Robert Love <rml@tech9.net>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [CFT] Bus mastering support for IDE CDROM audio
Date: Sun, 27 Jan 2002 13:36:51 -0800	[thread overview]
Message-ID: <3C5472F3.52549F23@zip.com.au> (raw)
In-Reply-To: <3C5119E0.6E5C45B6@zip.com.au> <1012166472.812.7.camel@phantasy>, <1012166472.812.7.camel@phantasy> <20020127222551.B7548@suse.de>

Jens Axboe wrote:
> 
> On Sun, Jan 27 2002, Robert Love wrote:
> > On Fri, 2002-01-25 at 03:40, Andrew Morton wrote:
> > > Reading audio from IDE CDROMs always uses PIO.  This patch
> > > teaches the kernel to use DMA for the CDROMREADAUDIO ioctl.
> > > [...]
> > > This code has not been tested for its effects upon SCSI-based
> > > CDROM readers.  It needs to be.
> >
> > Andrew,
> >
> > I wanted to confirm success of testing the patch with a SCSI CD-ROM
> > (Plextor UltraPlex Wide on aic7xxx).  I used your updated patch off your
> > website.
> >
> > Audio rip completed without error.  Performance seems the same, which I
> > assume is to be expected with SCSI readers.
> 
> sr already uses DMA for all transfers, so no performance gain was to be
> expected there. problem is ide-cd using pio for all packet command data
> transfers currently (modulo fs read write requests, of course)

Yup.  Rob was looking for regression - I'm not set up to test
SCSI CDROMs here.

The second patch goes back to reading a bunch of frames all
inside the same request, rather than one frame at a time.  This
is because the cdparanoia guys tell me that it can prevent
single-request overruns and underruns and other data loss which
occurs around the start and end of the request.  So with a walking-window
read algorithm from userspace they can pick up data which would
otherwise be lost.

Also it seems that some devices aren't happy with the larger transfers,
so it looks like the algorithm needs to become:

- Try multiple frames, DMA
- If that fails, try single frames, DMA
- If that fails, fall back to PIO

While all the time not altering the DMA status of the drive for
block-based filesystem I/O.

> not a whole lot of pio aic7xxx adapters out there :-)
> 

Thank heavens for that (I _knew_ I shouldn't have stuck my
nose in drivers/ide/).

-

  reply	other threads:[~2002-01-27 21:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25  8:40 [CFT] Bus mastering support for IDE CDROM audio Andrew Morton
2002-01-25 19:21 ` Kevin P. Fleming
2002-01-27  2:13   ` Dan Chen
2002-01-27  3:16   ` Andrew Morton
2002-01-27  6:41     ` Andrew Morton
2002-01-27  9:11       ` Kristian
2002-01-27 10:19         ` Kristian
2002-01-27 19:54           ` Ed Sweetman
2002-01-28  8:29             ` Andrew Morton
2002-01-28  9:51               ` benh
2002-01-28  9:51                 ` Andrew Morton
2002-01-28 15:50                   ` Ed Sweetman
2002-01-28 17:13                     ` Kristian
2002-01-28 13:51               ` Kristian
2002-01-28 19:21       ` Kevin P. Fleming
2002-01-26  8:43 ` Dan Chen
2002-01-26 12:03 ` Kristian
2002-01-27 21:21 ` Robert Love
2002-01-27 21:25   ` Jens Axboe
2002-01-27 21:36     ` Andrew Morton [this message]
2002-01-27 21:40     ` Robert Love

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=3C5472F3.52549F23@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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