Re: [ewg] [RFC] libibverbs: ibv_fork_init() and libhugetlbfs

2010-05-18 Thread Stefan Roscher
Hi Roland, On Wednesday 12 May 2010 06:40:16 pm Roland Dreier wrote: * added get_huge_page_size() to read the huge page size from /proc/meminfo. This is done at ibv_fork_init() time. That doesn't work on systems that have multiple huge page sizes (eg powerpc). You can compare the

Re: [RFC] libibverbs: ibv_fork_init() and libhugetlbfs

2010-05-12 Thread Roland Dreier
* added get_huge_page_size() to read the huge page size from /proc/meminfo. This is done at ibv_fork_init() time. That doesn't work on systems that have multiple huge page sizes (eg powerpc). You can compare the code to get the size in libhugetlbfs. Also I think the munging through

Re: [RFC] libibverbs: ibv_fork_init() and libhugetlbfs

2010-05-07 Thread Alexander Schmidt
On Thu, 06 May 2010 13:55:31 -0700 Roland Dreier rdre...@cisco.com wrote: I think that we cannot assume huge pages only come from libhugetlbfs -- we should support an application directly enabling huge pages (possibly via another library too, so we can't assume that an application knows the

[RFC] libibverbs: ibv_fork_init() and libhugetlbfs

2010-05-06 Thread Alexander Schmidt
Hi all, we are trying to make use of libhugetlbfs in an application that relies on ibv_fork_init() to enable fork() support. The problem we are running into is that calls to the madvise system call fail when registering a memory region for memory that is provided by libhugetlbfs. We have written