Re: less aggressive contigmalloc ?

看板FB_current作者時間13年前 (2012/08/24 02:01), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串5/11 (看更多)
On Thu, Aug 23, 2012 at 12:08:40PM -0500, Alan Cox wrote: .... > >yes i do see that. > > > >Maybe less aggressive with M_NOWAIT but still kills processes. > > Are you compiling world with MALLOC_PRODUCTION? The latest version of whatever the default is. But: > jemalloc uses significantly more memory when debugging options are > enabled. This first came up in a thread titled "10-CURRENT and swap > usage" back in June. > > Even at its most aggressive, M_WAITOK, contigmalloc() does not directly > kill processes. If process death coincides with the use of > contigmalloc(), then it is simply the result of earlier, successful > contigmalloc() calls, or for that matter any other physical memory > allocation calls, having depleted the pool of free pages to the point > that the page daemon runs and invokes vm_pageout_oom(). does it mean that those previous allocations relied on memory overbooking ? Is there a way to avoid that, then ? cheers luigi _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
文章代碼(AID): #1GDc_UvM (FB_current)
討論串 (同標題文章)
文章代碼(AID): #1GDc_UvM (FB_current)