lkml.org 
[lkml]   [2000]   [Mar]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: Endless overcommit memory thread.
    Date
    Followup to:  <38DC06D2.5D6A9CD@sgi.com>
    By author: Linda Walsh <law@sgi.com>
    In newsgroup: linux.dev.kernel
    >
    > I think there should be a 2nd system call with semantics like
    > 'vfork' or IRIX's sproc that explicitly allows data segment sharing
    > so only stack space needs to be allocated for the fork to work.
    > Current fork -- I lean toward not overcommitting -- it seems more
    > proper.
    >

    You mean like vfork()? Or clone()?

    -hpa
    --
    <hpa@transmeta.com> at work, <hpa@zytor.com> in private!
    "Unix gives you enough rope to shoot yourself in the foot."

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

    \
     
     \ /
      Last update: 2005-03-22 13:57    [W:0.028 / U:90.344 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site