mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Plail <plail@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: ide-2.4.19-ac4.11.patch, late but stable
Date: Fri, 16 Aug 2002 11:43:05 +0200	[thread overview]
Message-ID: <87fzxfxhp2.fsf@plailis.homelinux.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10208152353190.12468-100000@master.linux-ide.org> (Andre Hedrick's message of "Fri, 16 Aug 2002 00:01:52 -0700 (PDT)")

Hi Andre!

* Andre Hedrick writes:
>Greetings Markus,

>It is a fair question of which I do not have a nice answer.  I am
>working on fresh atapi-packet-generic engine but it is not a joy.
>There are oddities like bus-phases or bus-states which their setup and
>feeding of the DMA engine requires a more eligant hammer.

OK, I see. It's just that I stumbled across the patch for DMA audio CD
reading and thought that you perhaps have something similiar for
writing bigger block sizes. 

>As much as I hate to concept of a DMA mempool, it looks like the
>direction to follow.  Games such as HOST<>DEVICE || feast<>famine of
>buffer streams appear to be the norm to push vast amounts of atapi-dma.
>The alternative is to have device level request queues and have the
>queues carry the SG or PRD list for that portion.
>I am open to suggestions for direction.

I have to admit that I do not even have an idea what you are talking
about. I just think that this is a major drawback for Linux. CD writers
are as fast as 48x nowadays and DVD writers start getting more popular,
too, just as doing c2scans. So it is quite disappointing that it doesn't
work flawlessly with Linux.

regards
Markus


  reply	other threads:[~2002-08-16  9:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-15 13:18 Andre Hedrick
2002-08-16  6:47 ` Markus Plail
2002-08-16  7:01   ` Andre Hedrick
2002-08-16  9:43     ` Markus Plail [this message]
2002-08-16 10:48     ` Alan Cox

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=87fzxfxhp2.fsf@plailis.homelinux.net \
    --to=plail@web.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®