From: Jens Axboe <axboe@suse.de>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6 ide-cd DMA ripping
Date: Wed, 3 Mar 2004 13:25:06 +0100 [thread overview]
Message-ID: <20040303122506.GS9196@suse.de> (raw)
In-Reply-To: <200403031226.22015.s0348365@sms.ed.ac.uk>
On Wed, Mar 03 2004, Alistair John Strachan wrote:
> On Wednesday 03 March 2004 11:37, you wrote:
> > Hi,
> >
> > 2.6 still uses PIO for CDROMREADAUDIO cdda ripping, which is less than
> > optimal of course... This patch uses the block layer infrastructure to
> > enable zero copy DMA ripping through CDROMREADAUDIO.
> >
> > I'd appreciate people giving this a test spin. Patch is against
> > 2.6.4-rc1 (well current BK, actually).
> >
> [snip]
>
> Is this a general optimisation, i.e. will the rip methods used by
> cdda2wav and cdparanoia, etc. be optimised, or do you need some
> specific userspace tools to utilise it?
The patch only affects CDROMREADAUDIO ioctl. cdda2wav (with recent
libscg) will use SG_IO, which works equally well already. cdparanoia
uses CDROMREADAUDIO as well iirc, if it can use /dev/sg* sg v2
interface. I'm not completely sure, if you send me an strace of the
process in question I can tell you for sure :)
--
Jens Axboe
next prev parent reply other threads:[~2004-03-03 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 11:37 [PATCH] 2.6 ide-cd DMA ripping Jens Axboe
2004-03-03 11:45 ` Jens Axboe
2004-03-03 12:26 ` Alistair John Strachan
2004-03-03 12:25 ` Jens Axboe [this message]
2004-03-06 14:04 ` Sean Neakums
2004-03-07 10:35 ` Jens Axboe
2004-03-07 12:04 ` Sean Neakums
2004-03-08 9:41 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2004-03-04 11:07 Vince
2004-03-04 15:28 ` [PATCH] " Jens Axboe
2004-03-05 12:08 ` Colin Leroy
2004-03-05 12:21 ` Jens Axboe
2004-03-05 13:15 ` Colin Leroy
2004-03-05 13:22 ` Jens Axboe
2004-03-05 18:58 Voluspa
2004-03-07 10:34 ` Jens Axboe
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=20040303122506.GS9196@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
/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.