linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Paul Warren <pdw@ex-parrot.com>, Chris Wedgwood <cw@f00f.org>,
	itamar <itamar@ispbrasil.com.br>
Subject: Re: [uml-devel] Re: [uml-user] uml help __alloc_pages: 0-order allocation failed (gfp=0xf0/0)
Date: Tue, 22 Mar 2005 18:41:55 +0100	[thread overview]
Message-ID: <200503221841.55755.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050320222507.B15902@sphinx.mythic-beasts.com>

On Sunday 20 March 2005 23:25, Paul Warren wrote:
> [ trimmed cc to just -devel list]
>
> On Thu, Mar 17, 2005 at 08:49:38PM +0100, Blaisorblade wrote:
> > Paul Warren said that there is a leak in 2.4 UML related to hostfs
> > stuff.. and I already saw this message from some 2.4 recent UMLs. I hope
> > Paul Warren can explain what he saw and help us...
> >
> > In case we have confirmation it's hostfs-related, we only need to go back
> > to the stable 2.4.24-1um hostfs code (i.e. pre-humfs), as I already do in
> > the 2.4-bs tree.
>
> OK, our setup is that we have a load of distribution mirrors that are
> NFS mounted onto the host server.  The guests then mount these using
> hostfs.  We first noticed that a nightly updatedb was causing the amount
> of memory that could be malloced to decrease.  We found that doing a
> "find" across the entire hostfs mount also did the trick.
>
> I've attached the script and program that we used to meause the maximum
> amount of memory that can be malloced.  We then ran:
>
>  while : ; do ./maxalloc ; updatedb ; done
>
> ... and watched the memory leak away.

> Please let me know if you want some more info.
In priority order:
1) Try it on 2.6 and/or 2.4.27-bs (either bs1 or bs2-pre6, whichever you 
prefer and gives you less problems).
2) Try finding the item in /proc/meminfo (and if it's from Slab, 
inside /proc/slabinfo) which is increasing in the memory leak...
> Paul

-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade





-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2005-03-22 17:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 18:52 [uml-devel] uml help __alloc_pages: 0-order allocation failed (gfp=0xf0/0) itamar
2005-03-17 19:00 ` [uml-devel] Re: [uml-user] " Chris Wedgwood
2005-03-17 19:13   ` itamar
2005-03-17 19:25     ` Chris Wedgwood
2005-03-17 19:49       ` Blaisorblade
2005-03-20 22:25         ` Paul Warren
2005-03-22 17:41           ` Blaisorblade [this message]
2005-03-17 19:57     ` Paul Warren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200503221841.55755.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=cw@f00f.org \
    --cc=itamar@ispbrasil.com.br \
    --cc=pdw@ex-parrot.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox