This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hello, > Forget the rlimit issues, I've just used them to illustrate a problem > I had with malloc. OK. > Do I understand you correctly that you changed the meanings of the > environment variables MALLOC_MMAP_THRESHOLD_ and MALLOC_MMAP_MAX_ (and > the corresponding mallopt options) in a non compatible way - which > violates the documentation? The effect of MALLOC_MMAP_THRESHOLD_ isn't changed. I just want the default behaviour to be `address space completely allocatable', that's why I changed the meaning of MALLOC_MMAP_MAX_. > Playing around with MALLOC_MMAP_MAX I noticed that it's impossible to > switch off mmap completly. Do you really define this as a "feature" > of glibc 2.2? IMO it's a bug. OK, I see your point now, thanks. If setting MALLOC_MMAP_MAX_<=0 (whether via environment or via mallopt) would mean _no mmap whatsoever_, would that be enough (IIRC that's the way used in Emacs, for example)? I would submit a patch quickly then. I'll update the documentation as well. Regards, Wolfram.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |