From: Jeff Dike <jdike@addtoit.com>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: User-mode Linux Kernel Development
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] console and do_syscall_stub
Date: Wed, 23 Jan 2008 18:23:13 -0500 [thread overview]
Message-ID: <20080123232313.GA11799@c2.user-mode-linux.org> (raw)
In-Reply-To: <4797C6A5.1030408@nagafix.co.uk>
On Wed, Jan 23, 2008 at 10:58:45PM +0000, Antoine Martin wrote:
> [42949466.740000] do_syscall_stub : ret = -12, offset = 548682067984,
> data = 00000000606b1010
This usually means that a UML process hit the host's vm_area_struct limit.
Look at the host's /proc/sys/vm/max_map_count - the default is 64K,
which, given UML's propensity to map memory one page at a time, covers
256M of resident memory for a UML process.
I'd say double or quadruple it, depending on how much memory you think
a process can use. To be absolutely safe, make it big enough to cover
all of a UML's physical memory, since a process RSS can't exceed that.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2008-01-23 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 22:58 [uml-devel] console and do_syscall_stub Antoine Martin
2008-01-23 23:23 ` Jeff Dike [this message]
2008-01-24 23:20 ` Antoine Martin
2008-01-24 23:23 ` Antoine Martin
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=20080123232313.GA11799@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=antoine@nagafix.co.uk \
--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