public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Mark Mokryn <mark@sangate.com>
To: linux-kernel@vger.rutgers.edu, linux-scsi@vger.rutgers.edu,
	linux-mm@kvack.org
Subject: map_user_kiobuf problem in 2.4.0-test3
Date: Wed, 12 Jul 2000 18:40:56 +0300	[thread overview]
Message-ID: <396C9188.523658B9@sangate.com> (raw)

Hi,

Here's the scenario:
2.4.0-test3 SMP build running on a single 800MHz PIII (Dell GX-300)
After obtaining a mapping to a high memory region (i.e. either
PCI memory or physical memory reserved by passing mem=XXX to the kernel
at boot), I am trying to write a raw device with data in the mapped
region.
This fails, with map_user_kiobuf spitting out "Mapped page missing"
The raw write works, of course, if the mapping is to a kmalloc'ed
buffer.

I have tried the above with 2.2.14 SMP, and it works, so something in
2.4 is broken.
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%! This is very strange, since if the transfer rate was for some
unknown reason lower in the case of PCI (vs. high physical memory), then
one would expect the CPU utilization to be even lower, since the adapter
performs DMA. But instead, the CPU is sweating... So, it appears that
there's a problem in 2.2.14 as well, when the mapping is to PCI space...
Additionally, the max transfer rate of 8MB/s seems rather slow - don't
know why yet...

-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 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-12 15:40 Mark Mokryn [this message]
2000-07-12 16:08 ` map_user_kiobuf problem in 2.4.0-test3 Roman Zippel
2000-07-12 21:35   ` Mark Mokryn
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=396C9188.523658B9@sangate.com \
    --to=mark@sangate.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=linux-scsi@vger.rutgers.edu \
    /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