From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test9 breaks cdrecord w. ide-scsi device
Date: 21 Nov 2003 17:34:58 GMT [thread overview]
Message-ID: <bplic2$fdl$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 200311011219.21890.p_christ@hol.gr
In article <200311011219.21890.p_christ@hol.gr>,
P. Christeas <p_christ@hol.gr> wrote:
| > Hello
| >
| > ...
| >
| > There is now ide-cd writing support, and cdrecord 2 supports it. I build
| > that stuff modular, so I just load the ide-cd and isofs modules (modprobe
| > takes care of the rest). I achieve the fastest writing speeds I've ever
| > had, using this driver. Far better than ide-scsi or even Sleazy CD Creator
| > in Windows.
| >
| >...
|
| Tried it. Now used /dev/hdd there..
| This time it worked a few times and some other times it failed.
| It now seems that I got a buffer underrun, although I do have 'realtime
| priority' for the process.
| Note that I'm not using 'burnfree'. That's why I have linux anyway :) .
|
| Can anybody examine why is the buffer of cdrecord less than 100% with
| RR-scheduling? That would never happen in 2.4, cdrecord 1.10 ..
If you haven't solved this yet (firmware current?) you might try using a
large fifo, starting a burn, then looking at the system with vmstat to
see if there's a lot of system time. If so, I suspect the you are using
PIO in spite of the new method and selection of DMA for the device.
In any case it will provide a data point.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
prev parent reply other threads:[~2003-11-21 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 22:12 2.6.0-test9 breaks cdrecord w. ide-scsi device P. Christeas
[not found] ` <20031030171432.03dcaa76.mikeserv@bmts.com>
2003-10-31 15:35 ` P. Christeas
2003-11-01 10:19 ` P. Christeas
2003-11-21 17:34 ` bill davidsen [this message]
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='bplic2$fdl$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox