linux-um archives
 help / color / mirror / Atom feed
From: "James McMechan" <james_mcmechan@hotmail.com>
To: jdike@addtoit.com
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] many cow files with ubd_kern.c
Date: Sun, 29 Jan 2006 03:42:06 +0000	[thread overview]
Message-ID: <BAY101-F6796135F4986D1075AD47E2160@phx.gbl> (raw)
In-Reply-To: <20060129024620.GB7933@ccure.user-mode-linux.org>

Humm, I will look to see if that happens on my machines, nope
I just tested on a machine with more real memory but no skas3 no tmpfs I 
appear to have ~64M in use with one COW bitmap and 140M in use with 2 (from 
top in guest) the
other machine was shrinking the guest virtual address space to ~128M even 
when told to use 384M and the tmp(on tmpfs) was remounted with 
-oremount,size=10G

Though come to think of it the guest does not really need to have the 
vmalloced space
actually allocated with the backing file on tmp... but I can't think of a 
way to have it just mapped into high memory or something, but that would 
really be the place to put the 600M of bitmaps I expect to have if I can get 
things working.


>From: Jeff Dike <jdike@addtoit.com>
>To: James McMechan <james_mcmechan@hotmail.com>
>CC: user-mode-linux-devel@lists.sourceforge.net
>Subject: Re: [uml-devel] many cow files with ubd_kern.c
>Date: Sat, 28 Jan 2006 21:46:20 -0500
>
>On Sat, Jan 28, 2006 at 11:11:31PM +0000, James McMechan wrote:
> > allocation failed: out of vmalloc space - use "vmalloc=<size>" to 
>increse
> > size
> > Failed to vmalloc COW bitmap
> > ubd0: Can't open "COW0": errno -12
>
>I have a report (which I haven't looked into yet) of the ubd driver
>double-vmallocing the bitmap.  This is the call trace of the vmallocs
>as reported on IRC:
>
>ubd_add
>  enter
>Attempting to vmalloc COW bitmap \"cow0\" at
>  25600
>cow.bitmap = 0x00000000 (before vmalloc)
>abrooks
>  cow.bitmap = 0xa2800000 (after vmalloc)
>ubd_open enter
>  Attempting to vmalloc COW bitmap \"cow0\" at 25600
>cow.bitmap =
>  0xa2800000 (before vmalloc)
>cow.bitmap = 0xa280a000 (after
>  vmalloc)
>ubd_open exit
>  /dev/ubd/disc0: p1
>abrooks
>  ubd_close() enter
>ubd_close() exit
>ubd_close()
>  enter
>ubd_close() exit
>ubd_add exit
>
>				Jeff




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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:[~2006-01-29  3:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-28 23:11 [uml-devel] many cow files with ubd_kern.c James McMechan
2006-01-29  2:46 ` Jeff Dike
2006-01-29  3:42   ` James McMechan [this message]

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=BAY101-F6796135F4986D1075AD47E2160@phx.gbl \
    --to=james_mcmechan@hotmail.com \
    --cc=jdike@addtoit.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