From: Arjan van de Ven <arjanv@redhat.com>
To: Linh Dang <linhd@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mmap (2) vs read (2)
Date: Sat, 17 Sep 2005 14:26:35 -0400 [thread overview]
Message-ID: <1126981595.3010.1.camel@localhost.localdomain> (raw)
In-Reply-To: <wn58xxvhdz8.fsf@linhd-2.ca.nortel.com>
[-- Attachment #1: Type: text/plain, Size: 451 bytes --]
On Sat, 2005-09-17 at 12:10 -0400, Linh Dang wrote:
> Hi, how come reading memory from /dev/mem using pread(2) or mmap(2)
> will give diffent results?
because you're being evil ;)
mmap of /dev/mem for *ram* is special. To avoid cache aliases and other
evils, you can only mmap non-ram realistically on /dev/mem.
Why are you using /dev/mem in the first place, it's a sure sign that
you're doing something really wrong in your design...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-17 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 16:10 mmap (2) vs read (2) Linh Dang
2005-09-17 18:26 ` Arjan van de Ven [this message]
2005-09-18 16:47 ` Linh Dang
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=1126981595.3010.1.camel@localhost.localdomain \
--to=arjanv@redhat.com \
--cc=linhd@nortel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.