LKML Archive on
help / color / mirror / Atom feed
From: (Joerg Schilling)
Subject: Re: Again... DMA speed too slow
Date: Mon, 14 Apr 2008 19:19:04 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20080414175636.4ea815dc@core>

Alan Cox <> wrote:

> On Mon, 14 Apr 2008 18:54:22 +0200
> (Joerg Schilling) wrote:
> > >Which controller are you on?  I bet the recording itself will work fine
> > >on 48x.  It's probably that READ/WRITE BUFFERs are executed using PIO
> > >for compatibility reasons. 
> > 
> > If this happens inside Linux, Linux should be changed...
> The cases Linux falls back to PIO are the cases where the hardware isn't
> up to it, or reliably handling some DMA commands. Lots of that about in
> the PC world.

OK, I know that a few drives give wrong DMA speed test results on Solaris,
so the behavior for these drives seems to be unrelated to the OS.

Cdrecord is under constant development and for this reason, there are 
workareounds for these drives.

> > 2.01.01a38 is the latest. Install cdrecord suid root
> Remarkably brave ;)

I am not sure why you mention the term "brave", is it because all known Linux 
distributions still require suid root? In this case, I encourage you to inform 
yourself about the code quality of cdrecord. There was no known security problem 
during the past 4 years. Try to compare with other software ,-)

If you have problems with drives that implement no DMA with read buffer, just 

CDR_FORCESPEED=any cdrecord ......

Another way to deal with the problem is to create a file /etc/default/cdrecord
and to configure to use burnfree by default for the related drive.

e.g. by using a line:

optiarc=          1,0,0	-1	-1	burnfree

and call "cdrecord dev=optiarc ..."

If there is interest in having a way to force any speed without swiching on 
burnfree, I may add an option that may be used in /etc/default/cdrecord with the
same effect as CDR_FORCESPEED=any


-- (home) Jörg Schilling D-13353 Berlin                (uni)     (work) Blog:

  reply	other threads:[~2008-04-14 17:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 16:54 Joerg Schilling
2008-04-14 16:56 ` Alan Cox
2008-04-14 17:19   ` Joerg Schilling [this message]
2008-04-14 17:29     ` Alan Cox
2008-04-14 17:44       ` Alan
2008-04-14 18:28         ` Joerg Schilling
2008-04-14 18:21       ` Joerg Schilling
     [not found] <>
2008-03-31  0:59 ` Robert Hancock
  -- strict thread matches above, loose matches on Subject: below --
2008-03-30 21:53 J.A. Magallón
2008-04-02  7:16 ` Andrew Morton
2008-04-13  2:23   ` Tejun Heo

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: Again... DMA speed too slow' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).