From: "Sven Köhler" <skoehler@upb.de>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: hostfs / current->fsuid
Date: Wed, 23 Jun 2004 06:09:08 +0200 [thread overview]
Message-ID: <cbavp0$nss$1@sea.gmane.org> (raw)
In-Reply-To: <20040623004832.GD18570@thump.bur.st>
> Yes, however NFS has a remarkable ability to fuck up locking more often
> than not (at least on linux)
beside that, i think that the network-protocol could have been designed
much simpler and more firewall-friendly.
BTW: i am one of those, that think that NFS is faster than hostfs.
I cannot explain why, but i would guess, that - at least for parallel
file-access - the networking-code required less context-switches, since
the network-packets are perhaps queued before giving them to the
host-system.
That's just a guess, so you may prove me wrong ;-)
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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-06-23 4:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 3:44 [uml-devel] hostfs / current->fsuid Trent Lloyd
2004-06-22 13:50 ` Cameron Patrick
2004-06-22 18:35 ` BlaisorBlade
2004-06-23 0:48 ` Trent Lloyd
2004-06-23 4:09 ` Sven Köhler [this message]
2004-06-23 6:02 ` [uml-devel] " Trent Lloyd
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='cbavp0$nss$1@sea.gmane.org' \
--to=skoehler@upb.de \
--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