Hi Andreas,
Thank you very good comment.
> Having such notification handled by glibc to free up unused malloc (or
> any heap allocations) would be very useful, because even if a program
> does "free" there is no guarantee the memory is returned to the kernel.
Yes, no guarantee.
but current glibc
On Feb 10, 2008 01:46 +0900, KOSAKI Motohiro wrote:
> > This really needs to be triggered via a generic kernel event in the
> > final version - I picture glibc having a reservation API and having
> > generic support for freeing such reservations.
>
> to be honest, I doubt idea of generic reservat
On Sat 2008-02-09 11:07:09, Jon Masters wrote:
> This really needs to be triggered via a generic kernel
> event in the final version - I picture glibc having a
> reservation API and having generic support for freeing
> such reservations.
Not sure what you are talking about. This seems very ri
Hi Jon
> This really needs to be triggered via a generic kernel event in the
> final version - I picture glibc having a reservation API and having
> generic support for freeing such reservations.
to be honest, I doubt idea of generic reservation framework.
end up, we hope drop the application ca
This really needs to be triggered via a generic kernel event in the
final version - I picture glibc having a reservation API and having
generic support for freeing such reservations.
Jon
On Feb 9, 2008, at 10:55, "KOSAKI Motohiro" <[EMAIL PROTECTED]
> wrote:
this is usage example of /d
this is usage example of /dev/mem_notify.
Daniel Spang create original version.
kosaki add fasync related code.
Signed-off-by: Daniel Spang <[EMAIL PROTECTED]>
Signed-off-by: KOSAKI Motohiro <[EMAIL PROTECTED]>
---
Documentation/mem_notify.c | 120 +
6 matches
Mail list logo
