lkml.org 
[lkml]   [2002]   [Sep]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Good way to free as much memory as possible under 2.5.34?
Hi!

> > /*
> > * Try to free as much memory as possible, but do not OOM-kill anyone
> > *
> > * Notice: all userland should be stopped at this point, or livelock
> > is possible.
> > */
> >
> > This worked before -rmap came in, but it does not free anything
> > now. What needs to be done to fix it?
>
> Actually, it still worked when -rmap came in, but it stopped working
> when the LRU lists were made to be per-zone...
>
> > static void free_some_memory(void)
> > {
> > printk("Freeing memory: ");
> > while
> > (try_to_free_pages(&contig_page_data.node_zones[ZONE_HIGHMEM], GFP_KSWAPD, 0))
> > printk(".");
> > printk("|\n");
> > }
>
> Why don't you just allocate memory ?
>
> To prevent the OOM kill you can just check for a variable
> in the OOM slow path. No need to rely on any particular
> behaviour of the VM.

Allocating memory is pain because I have to free it afterwards. Yep I
have such code, but it is ugly. try_to_free_pages() really seems like
cleaner solution to me... if you only tell me how to fix it :-).

If it is not easy to fix, I can reintroduce memory eating code; but
I'd hate to special-case SWSUSP in VM. Otoh GFP_FAIL or something like
that might help me, right?
Pavel
--
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:28    [W:0.069 / U:0.104 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site