[lkml]   [2006]   [Feb]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH ] VMSPLIT config options (with default config fixed)
    On Sun, 2006-02-05 at 22:14 +0100, Jan Engelhardt wrote:
    > >> >
    > >> > Mmm.. bad idea. As much as I'd like the default to be 3GB_OPT, that would
    > >> > be a big impact to userspace, and there's no point in breaking everyone's
    > >> > machines when advanced users can just reconfig/recompile to get what they want.
    > >> >
    > >> What userspace programs do depend on it?
    > >
    > >there is a lot of userspace that assumes they can do 2Gb or even close
    > >to 3Gb of memory allocations. Databases, java, basically anything with
    > >threads. Sure for most of these its a configuration option to reduce
    > >this, but that still doesn't mean it's a good idea to change from the
    > >existing behavior...
    > >
    > Not to mention that these (almost(*)) fail anyway when you have less than 2
    > GB of RAM.

    it's not really overcommit... it can also be file mmaps or shared mmaps
    of say tmpfs files (the later is common with oracle actually)

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-02-05 22:21    [W:0.019 / U:19.948 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site