All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Marzot <gmarzot@nortelnetworks.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: Joe Marzot <gmarzot@nortelnetworks.com>,
	user-mode-linux-devel@lists.sourceforge.net,
	Randy Macleod <macleodr@nortelnetworks.com>
Subject: Re: [uml-devel] Q: UML thread communication - scheduling oddness
Date: Thu, 05 Aug 2004 09:35:01 -0400	[thread overview]
Message-ID: <41123785.5040004@nortelnetworks.com> (raw)
In-Reply-To: 200408050020.i750Kwvv009127@ccure.user-mode-linux.org

That's an excellent theory esp. ince we do not see the problem typically 
on a host with more memory. I presume there are tricks we can play to 
get our memory not to be swapped out (recall a discussion on that here).

Could you add a few sentences though on the delivery mechnisms for the 
the packets to the kernel thread and to userspace. I saw a poll() on the 
pollfds array which has the taps fd in it but this is a non-blocking 
poll and I could not trace to how often it is called and what triggers 
it - I also saw the sigio handler but I could not see who was generating 
the SIGIO - is that how the userspace thread is woken up?

If there is some thing else I can read to get some background that would 
help...otherwise its back to the source of course.

thank you kindly, Giovanni

Jeff Dike wrote:
> gmarzot@nortelnetworks.com said:
>  > That is, if I run a little busy loop
>  >   /mnt/plankton/stress --cpu 1 --io 1
>  > on the server side, the round trip time for messages is greatly
>  > *improved*. without this activity and a basically dormant server side
>  > UML the round trip times show considerable variabilty with gaps on the
>  >  order of seconds.
> 
> How's this for a theory:  The server's host is short on memory.  A UML 
> which
> is answering pings every second or so can be considered pretty idle, and 
> thus
> a good candidate to have its pages swapped out.  So, this happens, and when
> a ping comes in, UML needs to be swapped back in, causing your long and
> unpredictable delays.
> 
> Running a busy loop in the UML makes it busy from the point of view of the
> host and prevents it from being swapped out, giving you nice ping 
> latencies.
> 
>                                 Jeff
> 
> 





-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2004-08-05 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 20:10 [uml-devel] Q: UML thread communication - scheduling oddness Joe Marzot
2004-08-05  0:20 ` Jeff Dike
2004-08-05 13:31   ` Michael Richardson
2004-08-05 13:35   ` Joe Marzot [this message]
2004-08-05 17:23     ` Jeff Dike
2004-08-05 16:45   ` Joe Marzot
2004-08-05 19:17     ` Jeff Dike

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=41123785.5040004@nortelnetworks.com \
    --to=gmarzot@nortelnetworks.com \
    --cc=jdike@addtoit.com \
    --cc=macleodr@nortelnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.