hi,
A few more comments:
- AMAP_SHARED itself is a fine concept; it's used by shared memory.
sys/kern/sysv_shm.c:
452 error = uvm_map(vm-vm_map, attach_va, size, uobj, 0,
0,
453 UVM_MAPFLAG(prot, prot, UVM_INH_SHARE,
UVM_ADV_RANDOM,
On Tue, Nov 02, 2010 at 06:31:05AM +, YAMAMOTO Takashi wrote:
hi,
A few more comments:
- AMAP_SHARED itself is a fine concept; it's used by shared memory.
sys/kern/sysv_shm.c:
452 error = uvm_map(vm-vm_map, attach_va, size, uobj, 0,
0,
453
Chuck Silvers c...@chuq.com wrote:
- in getpages, rather than allocating a page of zeros for each file,
it would be better to use the same page of zeroes that mem.c uses.
if multiple subsystems need a page of zeroes, then I think that
UVM should provide this functionality
Am 02.11.10 02:00, schrieb David Young:
I'm working on a library called ppath(3) for making property lists more
convenient to use in the kernel. With ppath(3), you refer to a property
to read/write/delete in a property list by the path from the list's
outermost container. Comments welcome.
On Tue, Nov 02, 2010 at 01:35:10PM +0900, Masao Uebayashi wrote:
If a small program has both .data and .bss, and if .data is small,
I'd use .rodata and copy it to .bss explicitly, so that resulting
process allocates only .bss anon instead .data + .bss.
Why don't you do the reverse and drop
On Mon, Nov 01, 2010 at 08:00:09PM -0500, David Young wrote:
I'm working on a library called ppath(3) for making property lists more
convenient to use in the kernel. With ppath(3), you refer to a property
to read/write/delete in a property list by the path from the list's
outermost
