| raw e-mail | index | archive | help
so didn't need an explicit NUMA configuration parameter. In C one would use cpuset_setdomain(2) instead, but that's not as convenient. So, imbuing a NUMA domain in struct shm_largepage_conf is still probably a reasonable thing to do. > It should be very easy to implement: extend shm_largepage_conf to > include a NUMA domain parameter, and specify that domain when allocating > pages for the object (in shm_largepage_dotruncate(), the > vm_page_alloc_contig() call should become a > vm_page_alloc_contig_domain() call). > > > Otherwise, in a perfect world, I'd like a unified interface for both > > Linux and FreeBSD. Linux hugepages are managed using standard system calls; > > files are mmap(2)'d into virtual address space from hugetlbfs and > > ftruncate(2)'d. > > largepage shm objects work this way as well. > > > A matching interface would not add an extra kernel > > entrypoint and even more importantly, it would ease the Linux-to-FreeBSD > > porting process for programs that use hugepages.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>