From: Wes Janzen <superchkn@sbcglobal.net>
To: Stuart Longland <stuartl@longlandclan.hopto.org>
Cc: iain d broadfoot <ibroadfo@cis.strath.ac.uk>,
lkml <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@suse.de>
Subject: Re: getting a working CD-drive in 2.6
Date: Sat, 13 Sep 2003 02:41:53 -0500 [thread overview]
Message-ID: <3F62CA41.3040900@sbcglobal.net> (raw)
In-Reply-To: <1063436241.3f62bfd163b32@www.longlandclan.hopto.org>
Stuart Longland wrote:
>Quoting Wes Janzen <superchkn@sbcglobal.net>:
>
>
>
>>Hi,
>>
>>Actually with 2.6, you no longer need ide-scsi. You'll need to upgrade
>>your cdrecord tools and probably your burning GUI, if you use one....
>>
>>
>>
>
>Ahh okay, I wasn't aware of that. We use a SCSI burner anyways, but most of my...
>
>
>
And here's an even better reason to avoid ide-scsi in 2.6 (Jens sent
this to the list, but I don't see it...):
>Jens Axboe wrote:
>
>
>
>That's because it _is_ faster. It contains no silly memory allocations
>for the buffer and data copying in the kernel, the data is mapped from
>the user buffer and DMA'ed directly from there. It also uses DMA where
>ide-scsi wont.
>
>People generally report that they have no problems burning at full speed
>(52) on even really old machines where ide-scsi maxed out long before.
>
>
>
Certainly that is true. The system was nearly unresponsive at 16X (on
2.4.18 SuSE) with my K6-2 400, but I can set it up to 32X now and I have
no problems. My recorder never hits 32X with my media though, maxes out
at around 20X but I can browse the web while burning with absolutely no
fear of my buffer running dry (probably helps that it's a 8MB buffer but
cdrecord still never reports it being low). That's a big change from 2.4.
-Wes Janzen-
next prev parent reply other threads:[~2003-09-13 7:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 9:38 getting a working CD-drive in 2.6 iain d broadfoot
2003-09-13 2:08 ` Stuart Longland
2003-09-13 2:59 ` Wes Janzen
2003-09-13 6:29 ` Jens Axboe
2003-09-13 6:57 ` Stuart Longland
2003-09-13 7:41 ` Wes Janzen [this message]
2003-09-17 11:53 ` Pau Aliagas
2003-09-13 2:59 ` Wes Janzen
2003-09-13 9:50 ` iain d broadfoot
2003-09-13 15:21 ` iain d broadfoot
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=3F62CA41.3040900@sbcglobal.net \
--to=superchkn@sbcglobal.net \
--cc=axboe@suse.de \
--cc=ibroadfo@cis.strath.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=stuartl@longlandclan.hopto.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.