From: "Steve Schmidtke" <steve_schmidtke@hotmail.com>
To: doug@easyco.com
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] filemap feature 2.4.22-5um
Date: Tue, 14 Oct 2003 14:08:57 +0000 [thread overview]
Message-ID: <BAY7-F125P4zi6UUG7W0000f8fc@hotmail.com> (raw)
Doug Dumitru wrote:
>A couple of questions. I noticed that you are not mapping /proc/mm.
[...]
>This looks like one per virtual process (minus threads). Am I reading this
>right.
yes. The discussion for a previous patch considered a "mm" table to hold a
pool of /proc/mm files to handle one fd per process. One side effect of
this would place a hard limit on the number of processes in the UML: the
number of /proc/mm files opened. I'm not sure what side effects re-using
/proc/mm files would have, either. I should have mentioned TT/SKAS issues,
but it slipped my mind (I only use TT mode). So to use skas in a chroot,
you'll still have to mount /proc/mm in there. Hopefully Jeff has a fix for
/proc/mm in the works.
>On virtuals that I run, I tend to only see a single "vm" file opened:
yup. Things have changed since I looked at it for the last filemap patch
*sigh*. It used to be 1 file for every 256M of memory, but now, it is just
one big happy file, so in SKAS mode you should need only one vm file entry.
In TT mode there are a few more files required, but the max now seems to be
3 or 4 entries.
>Is there any reason the tun/tap networking wouldn't work with this layout
>by pre-opening /dev/net/tun.
Possibly, but you will have to check out the "TUN/TAP with a preconfigured
tap device" section of the virtual networking howto as the uml_net helper
won't pick up the filemapped fd for /dev/net/tun inside a chroot (nor will
it likely have ifconfig or route binaries available). Let me know if you
get this to work.
Steve Schmidtke
_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2003-10-14 14:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 14:08 Steve Schmidtke [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-18 17:15 [uml-devel] filemap feature 2.4.22-5um Steve Schmidtke
2003-10-18 16:34 BlaisorBlade
2003-10-18 1:31 Steve Schmidtke
2003-10-18 12:37 ` Henrik Nordstrom
2003-10-18 21:57 ` Goetz Bock
2003-10-18 22:29 ` Henrik Nordstrom
2003-10-18 14:27 ` Adam Heath
2003-10-14 22:58 Steve Schmidtke
2003-10-15 8:43 ` azu
2003-10-15 20:13 ` Jeff Dike
2003-10-14 3:54 Steve Schmidtke
2003-10-13 5:15 ` Jeff Dike
2003-10-14 6:19 ` Doug Dumitru
2003-10-17 17:14 ` Adam Heath
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=BAY7-F125P4zi6UUG7W0000f8fc@hotmail.com \
--to=steve_schmidtke@hotmail.com \
--cc=doug@easyco.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