lkml.org 
[lkml]   [1998]   [Oct]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 'disposable' dirty pages [was: Out Of Memory in v. 2.1]
Date
>>>>> "Chris" == Chris Wedgwood <chris@cybernet.co.nz> writes:
> - - how does libc tell the application that this area of memory needs
> to be recreated?

It doesn't. It would only mark free'd pages as disposable.
Pages that the application is not supposed to use anyway.
Of course, I'm not quite sure how much better this would be compared to having
a malloc library that returns unused pages to the OS. Maybe the `return unused
page + realloc a page' would be noticeably more expensive than just `mark
disposable' ?

> Also - how does this differ from above, assuming here libc catches
> ENONMEM and free's the 'disposable mappings' itself?

Well, disposing of disposable pages can be done without application involvement
(at the OOM time) which makes a big difference since when you're out of memory,
your application's ENOMEM handler would probably fail.


Stefan

-
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:44    [W:0.390 / U:0.932 seconds]
©2003-2014 Jasper Spaans. Advertise on this site