lkml.org 
[lkml]   [2003]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 2.2/2.4/2.6 VMs: do malloc() ever return NULL?
    On Wed, Nov 26, 2003 at 02:20:58PM +0100, Ihar 'Philips' Filipau wrote:
    > So what do you use then in user space to reliably allocate memory?
    > As to me - memory is a resource. Is it virtual or is it physical - it
    > is still resource. And I need to allocate part of this resource.
    > malloc() uses brk() inside. But brk() is "implementation details". I
    > honestly do not care about them - I just want to be sure that what ever
    > resource I have allocated - I can use it afterwards until I shall free
    > it. POSIX even doesn't mention brk() BTW.
    > If you can hint me any other method to allocate memory without
    > surprises - I will really appreciate.

    Non-overcommit is one such method at the kernel level.
    mlockall(MCL_CURRENT|MCL_FUTURE) is another (requiring support at both
    levels, in addition to administrative grants of privilege).


    -- wli
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:58    [W:4.566 / U:0.028 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site