From: Michel Hubert <mhubert@matrox.com>
To: linux-mm@kvack.org
Subject: [Fwd: remap_page_range() vs nopage()]
Date: 14 Jul 2004 18:43:06 -0400 [thread overview]
Message-ID: <1089844986.15840.144.camel@blackcomb> (raw)
Hello,
I previously posted this question to kernelnewbies.org but without
getting any answer. I hope it is not too basic for this mailing list...
It's written in Linux Device Driver 2nd edition that remap_page_range
(which maps an entire range at once) should be used for device IO
whereas nopage (which maps a single page at a time) should be used for
real physical memory.
However, I noticed that mmap_mem() in drivers/char/mem.c uses
exclusively remap_page_range. How could this work when dealing with non
contiguous physical memory ?
Thank you,
Michel
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next reply other threads:[~2004-07-14 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 22:43 Michel Hubert [this message]
2004-07-14 22:56 ` William Lee Irwin III
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=1089844986.15840.144.camel@blackcomb \
--to=mhubert@matrox.com \
--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