|
[openbeos]
||
[Date Prev]
[09-2002 Date Index]
[Date Next]
||
[Thread Prev]
[09-2002 Thread Index]
[Thread Next]
[openbeos] Re: mmap, vm2 and you
- From: "Michael Phipps" <mphipps1@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sat, 07 Sep 2002 16:59:11 -0400
>Kernel newbie question: what will the kernelland counterpart
>to userland mmap() be called? (the BeOS current map_memory()
>call used by accelerant's drivers I mean).
>
>At any rate, that one will definitely need the "straight forward"
>version of mapping, in the context of accelerants (ie in the context
>of mapping "memory" to memory), no funky copy-on-write feature there.
Right now, in my implementation, it is called mmap. The syscall would call the
kernel land version.
Accelerants would not use mmap. They would use an area call. Using mmap as a
thousand different
things is a unix-ism, really. They use it to allocate memory, share data, etc.
|
|
