From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fun with cfs.
Date: Wed, 12 Jan 2005 19:33:05 +0100 [thread overview]
Message-ID: <58788bdc3f16ccde4cd9c19600229a1b@plan9.escet.urjc.es> (raw)
In-Reply-To: <Pine.LNX.4.58.0501121117480.3521@bluesteel.lanl.gov>
[-- Attachment #1: Type: text/plain, Size: 89 bytes --]
You have iostats and the -D flag in ramfs.
Isn't that what you want? Or am I sleeping?
[-- Attachment #2: Type: message/rfc822, Size: 3533 bytes --]
From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] fun with cfs.
Date: Wed, 12 Jan 2005 11:26:30 -0700 (MST)
Message-ID: <Pine.LNX.4.58.0501121117480.3521@bluesteel.lanl.gov>
I've been playing around with lib9p and then started looking at cfs. You
can do something with cfs that is kind of fun.
I can send patches if anyone wants them.
Basically, you rip all the caching out of cfs and you have a very nice
tutorial program for seeing how 9p works. Took about 15 mins. You end up
with cfs.c and (IIRC) stats.h or some such, so you get one .c file and you
can then:
./cfs -S -d il!yourhost
And you get this nice mountpoint, which you can cd to, ls, to things in
inside of .... all while watching the 9p traffic so you can see how it
works. Good fun.
It would be great for showing people how 9p works or for classes. Even
better is letting poor suffering students do the same thing with nfs, and
then with 9p; you really start to appreciate 9p if you've done a lot of
NFS (which I have ...).
Now here's where somebody tells me: that file system already exists, just
do x and y and z; so, if this is useless, well, I had fun anyway; if not,
then I'll send the c-diffs as they are very short.
thanks
ron
next prev parent reply other threads:[~2005-01-12 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 18:26 Ronald G. Minnich
2005-01-12 18:33 ` Fco. J. Ballesteros [this message]
2005-01-12 18:37 ` Ronald G. Minnich
2005-01-12 21:38 ` Russ Cox
2005-01-12 21:43 ` Ronald G. Minnich
2005-01-12 23:30 ` Charles Forsyth
2005-01-12 23:21 ` Ronald G. Minnich
2005-01-13 0:06 ` Russ Cox
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=58788bdc3f16ccde4cd9c19600229a1b@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).