Re: Commenting out out_of_memory() function in __alloc_pages()

Chase Venters wrote:
> On Tue, 11 Jul 2006, Abu M. Muttalib wrote:
> > I fail to understand that why the OS doesn't return NULL as per man
> > pages of malloc. It insteat results in OOM.
>
> If you want strict malloc(), you can use the sysctl to turn off
> overcommit. It's even appropriate to do so for certain applications.

The problem is, there is no way to turn off overcommit completely.

Arjan said something about shared libs depending on overcommit :(

Thanks!

--
Al

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

References:
- RE: Commenting out out_of_memory() function in __alloc_pages()
  - From: "Abu M. Muttalib" <[email protected]>
- RE: Commenting out out_of_memory() function in __alloc_pages()
  - From: Chase Venters <[email protected]>

Prev by Date: Re: tty's use of file_list_lock and file_move
Next by Date: Re: [RFC] VFS: FS CoW using redirection
Previous by thread: RE: Commenting out out_of_memory() function in __alloc_pages()
Next by thread: RE: Commenting out out_of_memory() function in __alloc_pages()
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]