From: Jeff Dike <jdike@addtoit.com>
To: Joe Marzot <gmarzot@nortelnetworks.com>
Cc: 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 15:17:13 -0400 [thread overview]
Message-ID: <200408051917.i75JHDCi003746@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 05 Aug 2004 12:45:04 EDT." <41126410.6040008@nortelnetworks.com>
gmarzot@nortelnetworks.com said:
> thinking about this a bit more...some doubts...note: the regular
> 'pings' which are serviced purely by kernel resident code/ kernel
> thread do not exhibit the delays. It is only when the communication
> involved a userspace app as the responder to the 'app-level-ping'
> that the delays come. Is the memory for the userspace app seperately
> swappable from that of the kernel thread?
The userspace app is all of UML, including the parts of the kernel which
respond to pings. It can all be swapped out by the host.
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
prev parent reply other threads:[~2004-08-05 18:17 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
2004-08-05 17:23 ` Jeff Dike
2004-08-05 16:45 ` Joe Marzot
2004-08-05 19:17 ` Jeff Dike [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=200408051917.i75JHDCi003746@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=gmarzot@nortelnetworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox