linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mark Mokryn <mark@sangate.com>
To: Roman Zippel <roman@augan.com>
Cc: linux-kernel@vger.rutgers.edu, linux-scsi@vger.rutgers.edu,
	linux-mm@kvack.org
Subject: Re: map_user_kiobuf problem in 2.4.0-test3
Date: Wed, 12 Jul 2000 23:35:38 +0200	[thread overview]
Message-ID: <396CE4AA.12C08C62@sangate.com> (raw)
In-Reply-To: <396C97F7.2AEE5FE7@augan.com>

Hi again,

Roman Zippel wrote:
> > On another interesting note: The raw devices I'm writing to are Fibre
> > Channel drives controlled by a Qlogic 2200 adapter (in 2.2.14 I'm using
> > the Qlogic driver). When writing large sequential blocks to a single
> > drive, I reached 8MB/s when the memory was mapped to the high reserved
> > region, while CPU utilization was down to about 5%. When the mapping was
> > to PCI space, I was able to write at only 4MB/s, and CPU utilization was
> > up to 60%!
> 
> The data is copied from a buffer to the pci device. DMA transfers going
> directly to pci space is impossible without (small) changes to 2.2. 2.4
> has the theoretic possibility to do it and checks already for that, but
> how it should be done practically I'd like to know too.

Okay - if you're right, then this explains the poor performance I'm
seeing for PCI-PCI raw I/O on 2.2.14... Raw I/O is senseless if bounce
buffers are used. Still, raw I/O (the kiobuf stuff) seems to be quite
broken on 2.4.0t3...

-Mark
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-07-12 21:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-12 15:40 Mark Mokryn
2000-07-12 16:08 ` Roman Zippel
2000-07-12 21:35   ` Mark Mokryn [this message]
2000-07-14 10:31 ` Stephen C. Tweedie

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=396CE4AA.12C08C62@sangate.com \
    --to=mark@sangate.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=linux-scsi@vger.rutgers.edu \
    --cc=roman@augan.com \
    /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