From: Jeff Dike <jdike@addtoit.com>
To: roland <for_spam@gmx.de>
Cc: Joern Bredereck <jb@bw-networx.net>,
user-mode-linux-user@lists.sourceforge.net,
user-mode-linux-devel@lists.sourceforge.net, mingo@elte.hu
Subject: [uml-devel] Re: [uml-user] Network lags
Date: Fri, 09 Apr 2004 12:26:52 -0400 [thread overview]
Message-ID: <200404091626.i39GQqsf002414@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Fri, 09 Apr 2004 14:47:32 +0200." <189201c41e30$d434cc70$2000000a@schlepptopp>
for_spam@gmx.de said:
> at least, i would be interested in getting to know:
> - why this happens
> - how to "tune" this, that it doesn`t happen
> - if this is expected behavour on "heavy loaded systems" or probably a uml
> or host-kernel bug
As you said, you're making life hard for the host.
My guess as to what's happening is this.
You're generating a ton of IO which is pulling the host's memory into page
cache. This causes UML to get swapped out because it's not doing anything
except answering a ping once in a while. When it does have to answer a ping,
it needs to be swapped back in, which might be hard since you're sucking down
a lot of IO bandwidth.
So, I don't think this says too much about whether anything's wrong with
either the host or UML.
Once thing you might try is do the same IO with O_DIRECT. That won't pollute
the page cache.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&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
next prev parent reply other threads:[~2004-04-09 16:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.59.9.0404091209570.10714@hathi.bw-networx.net>
[not found] ` <185d01c41e23$5996cc00$2000000a@schlepptopp>
2004-04-09 12:47 ` [uml-devel] Re: [uml-user] Network lags roland
2004-04-09 16:26 ` Jeff Dike [this message]
2004-04-09 18:33 ` [uml-devel] uml responsivenes or "AS vs DEADLINE Scheduler on uml-host" - was: " roland
2004-04-10 12:28 ` BlaisorBlade
2004-04-13 21:26 ` roland
2004-04-14 1:02 ` Henrik Nordstrom
[not found] ` <c58kbu$el1$1@sea.gmane.org>
2004-04-10 14:08 ` [uml-devel] " Jeff Dike
2004-04-10 14:00 ` Sven Köhler
2004-04-10 17:07 ` Jeff Dike
2004-04-10 21:22 ` Sven Köhler
2004-04-10 23:29 ` Henrik Nordstrom
2004-04-11 3:45 ` attriel
2004-04-15 0:31 ` roland
2004-04-15 12:01 ` David Cannings
[not found] ` <407EADE0.8010308@cox.net>
2004-04-15 21:11 ` roland
2004-04-16 15:12 ` Matthew Bloch
2004-04-18 10:54 ` roland
2004-04-10 14:50 ` [uml-devel] Re: V=R Michael Koehne
2004-04-11 16:54 ` BlaisorBlade
2004-04-11 17:17 ` Nicholas E. Walker
2004-04-10 15:12 ` [uml-devel] Re: [uml-user] Network lags Nicholas E. Walker
2004-04-10 16:46 ` Steven Pritchard
2004-04-10 23:41 ` Henrik Nordstrom
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=200404091626.i39GQqsf002414@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=for_spam@gmx.de \
--cc=jb@bw-networx.net \
--cc=mingo@elte.hu \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@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