hi, >> Findings after having run the system for a while and having about 1.1gig >> in the pool(9)s: >> Option a: about 30000 allocated kernel map_entries (not in the map but >> allocated) >> Option b: about 100000 allocated boundary tags. >> Option c: about 400000 allocated boundary tags. >> >> With boundary tags beeing about half the size of vm_map_entries the vmem >> version uses slightly more memory but not so much.
why did you use different numbers for heap_va_arena's qcache_max (8 * PAGE_SIZE) and VMK_VACACHE_MAP_QUANTUM (32 * PAGE_SIZE)? if i read your patches correctly, the number of map entries/boundary tags will be smaller if these constants are bigger, right? >> Both versions use a modified kmem(9) that interfaces either with vmem or >> the extended kva caches, which has page_aligned memory for allocations >> of page_size and larger and cache_line aligned allocations for >> allocations between cache_line size and page_size. >> This should resolve some problems xen-kernels do have. does the original (solaris) version of kmem_alloc provide aligned allocations? YAMAMOTO Takashi
