linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Quinn <cq@htec.demon.co.uk>
To: linux-mm@kvack.org
Subject: mmap and raw disk devices...
Date: Thu, 18 Oct 2001 16:59:02 +0100	[thread overview]
Message-ID: <3BCEFC46.9E8FEF7A@htec.demon.co.uk> (raw)

Hello list,

I tried to mmap a disk partition raw device which failed.
Can anyone tell me the reason mmap does not support such a
device? 
I would have thought a mmap/raw-device combination to be ideal as
a basis for a high performance database system.
I know there is the option of managing memory<->disk movements
oneself, but my understanding is that handling page-faults via
signal trap handling is *very* expensive. Far better to leave
such matters in the hands of the OS.

I suspect there is some fundamental reason for not mmap'ing raw
devices that is patently obvious to everyone but me! 

Thanks,
Chris Quinn
--
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-mm.org/

             reply	other threads:[~2001-10-18 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 15:59 Christopher Quinn [this message]
2001-10-19 14:46 ` Eric W. Biederman

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=3BCEFC46.9E8FEF7A@htec.demon.co.uk \
    --to=cq@htec.demon.co.uk \
    --cc=linux-mm@kvack.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