|To:||Dan Malek <firstname.lastname@example.org>|
|Subject:||Re: Why is mmap()ed reserved memory so slow?|
|From:||David Chau <email@example.com>|
|Date:||Mon, 18 Jul 2005 10:44:00 -0400|
|User-agent:||Mozilla Thunderbird 1.0.2-1.3.3 (X11/20050513)|
Dan Malek wrote:
How about a little more info, like what kernel are you using and what are the parameters you are sending to mmap()?
Linux (none) 2.4.31 #412 SMP Fri Jul 15 16:26:05 EDT 2005 mips unknown (unmodified kernel from linux-mips.org). It's running on the SB1 on a Broadcom 1250 board. I mmap() with: int mem_fd = open("/dev/mem", O_RDWR); void* mem_base = mmap(NULL, DRIVER_MEM_SIZE, PROT_READ | PROT_WRITE, MAP_SHARED, mem_fd, DRIVER_MEM_PHYS_BASE); Where driver_mem_phys_base = 253M, and driver_mem_size=1M.
The better way to approach this is to place an mmap() function in the associated driver that works in conjunction with the application to gain shared access as you expect. This also closes a hole where an errant application could write into unexpected places through /dev/mem.
Could you point me to an example of this so I can figure out how to do it? Thanks, David
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||undefined symbol '__divdi3' & '__moddi3' on linux kernel 2.6.10 (toolchain Linuxi386/Mips32), David Sanchez|
|Next by Date:||glibc syscall patch, Jim Gifford|
|Previous by Thread:||Re: Why is mmap()ed reserved memory so slow?, Dan Malek|
|Next by Thread:||Re: Why is mmap()ed reserved memory so slow?, Ralf Baechle|
|Indexes:||[Date] [Thread] [Top] [All Lists]|