From: Rob Landley <rob@landley.net>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Gerd Knorr <kraxel@bytesex.org>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] SIGSEGV and SA_NODEFER
Date: Tue, 25 Jan 2005 12:30:03 -0500 [thread overview]
Message-ID: <200501251230.04080.rob@landley.net> (raw)
In-Reply-To: <200501251240.35872.blaisorblade@yahoo.it>
On Tuesday 25 January 2005 06:40 am, Blaisorblade wrote:
> > Host is swapping, client configured without even support for swap. (If I
> > can get the darn client vmlinux down to 1 megabyte, I'd be thrilled.
> > Didn't somebody once make the entire block layer configurable out once?
> > With hostfs, I don't need it...)
>
> Do you trust hostfs so much? You don't need user IDs on your FS, I guess.
Once I get /dev on ramfs managed by udev? Not really, no. I need the
permissions to be right, but just about everything else should belong to
root. (Yeah, there are a couple fun tricks where files change their
ownership to some variant of "nobody" to do chroot jails and stuff, but they
do that at runtime...)
I've probably missed one or two instances, but I expect I can work around
'em...
> I'm not at all happy with this, but I don't want someone using hostfs over
> its possibilities. NFS is much better, anyway.
NFS gives me hives (a stateless fileserver: okay, spot the contradiction in
terms here), although I must admit I haven't tried the new TCP/IP based
version (V4?) yet because it wasn't finished last time I tried.
> And somebody says it's also
> faster (and since hostfs does limited caching, it makes sense - hostfs must
> avoid having any inode cache, since it closes the host fd only when the
> inode is evicted from the cache; I don't think it's possible to cache data
> without an inode to link to, so it's clear it's slow).
Since the host is cacheing the data for us, not having a redundant cache
sounds like a good idea to me. Admittedly, it's more syscalls, but less
memory consumption...
Rob
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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:[~2005-01-25 18:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 21:28 [uml-devel] SIGSEGV and SA_NODEFER Jeff Dike
2005-01-20 0:07 ` Blaisorblade
2005-01-20 3:52 ` Rob Landley
2005-01-21 12:35 ` Blaisorblade
2005-01-21 18:18 ` Rob Landley
2005-01-21 19:58 ` Blaisorblade
2005-01-22 16:34 ` Rob Landley
2005-01-24 19:45 ` Blaisorblade
2005-01-25 1:38 ` Rob Landley
[not found] ` <20050125084506.GA562@bytesex>
2005-01-25 10:16 ` Blaisorblade
2005-01-25 10:16 ` Rob Landley
2005-01-25 11:40 ` Blaisorblade
2005-01-25 17:30 ` Rob Landley [this message]
2005-01-25 19:34 ` Blaisorblade
2005-01-25 19:30 ` Rob Landley
2005-01-25 20:50 ` Blaisorblade
2005-01-25 22:43 ` Rob Landley
2005-01-21 13:09 ` Blaisorblade
2005-01-21 16:56 ` 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=200501251230.04080.rob@landley.net \
--to=rob@landley.net \
--cc=blaisorblade@yahoo.it \
--cc=kraxel@bytesex.org \
--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.