From: Markus Plail <linux-kernel@gitteundmarkus.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21 ServerWorks DMA Bugs
Date: Sat, 05 Jul 2003 09:21:13 +0200 [thread overview]
Message-ID: <87fzllh21i.fsf@gitteundmarkus.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0307042325430.3837@mackman.net> (Ryan Mack's message of "Fri, 4 Jul 2003 23:45:29 -0700 (PDT)")
On Fri, 4 Jul 2003, Ryan Mack wrote:
> I've real the other threads but nothing touches on my specific issue.
> I have a dual P4 Xeon Dell PowerEdge 1600SC with a Fusion MPT SCSI
> controller and a ServerWorks CSB5 IDE chipset. All the HDs are on the
> SCSI bus, and only my CD reader and my DVD writer are on the IDE bus
> (one on each channel). Hyperthreading is enabled (4 logical
> processors). I am using GCC 3.2.2.
>
> The CD readers is the blacklisted 'SAMSUNG CD-ROM SC-148C' and I never
> use it so I can remove it if needed. The DVD writer is a 'SONY DVD RW
> DRU-500A'. Both are going through the ide-scsi driver. Whenever I
> read/write CDs in the DVD writer, I get very high system load (50% on
> one CPU), even though DMA seems to be enabled.
If you are writing CDs with unusual block sizes (audio CDs, (S)VCDs,
RAW mode -> blocksize != 2048) you won't get DMA with ide-scsi, no
matter what you do. It's simply not supported.
regards
Markus
next prev parent reply other threads:[~2003-07-05 7:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 6:45 2.4.21 ServerWorks DMA Bugs Ryan Mack
2003-07-05 6:49 ` Andre Hedrick
2003-07-05 7:21 ` Markus Plail [this message]
2003-07-05 16:58 ` Ryan Mack
2003-07-05 17:07 ` Jeff Garzik
2003-07-06 7:40 ` Alan Cox
2003-07-06 9:06 ` Tomas Szepe
2003-07-06 9:10 ` Alan Cox
2003-07-06 11:10 ` Tomas Szepe
2003-07-06 11:38 ` Alan Cox
2003-07-06 16:42 ` Vojtech Pavlik
2003-07-06 17:49 ` Alan Cox
2003-07-07 0:42 ` Andre Hedrick
2003-07-07 3:42 ` Tomas Szepe
2003-07-07 6:42 ` Alan Cox
2003-07-07 8:49 ` Tomas Szepe
2003-07-07 8:13 ` Andre Hedrick
2003-07-07 8:17 ` Andre Hedrick
2003-07-07 8:45 ` Tomas Szepe
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=87fzllh21i.fsf@gitteundmarkus.de \
--to=linux-kernel@gitteundmarkus.de \
--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 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.