Arjan van de Ven <[email protected]> wrote:
> 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...
Thanx for the reply, what I'm doing is writing a driver (based on
mem.c) to export a block of ram to (other masters on) the PCI bus. The
driver does:
1. get a contiguous block of ram using alloc_pages()
2. export (via host-bridge hw setting) the block to the pci
bus
3. provide the .mmap() method in the driver to let userspace
to mmap the device
In doing so, I encountered the inconsistencies of mmap(2) vs
read(2)/write(2). The work around I found is to SetPageReserved() on
all the pages got from alloc_pages(). But unfortunately I have no
clues why it's so. The vm code is not the easiest one to read
(compared to let's say the network code.)
--
Linh Dang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |