From: YAMANASHI Takeshi <9.nashi@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] run and mount
Date: Tue, 2 Aug 2005 09:46:19 +0900 [thread overview]
Message-ID: <f84728e25a2cc74ca06423ace4414326@orthanc.cc.titech.ac.jp> (raw)
> You can estimate for computing power to do this.
:
> The result measured on 2.4GHz Xeon
:
> 41 years on single computer!
Hehe, I haven't seriously estimated the time needed
to complete the job. 41 years? That's great.
I would see the possibitily of volunteer based
computing when it got as common as p2p file sharing. :)
> 500 volunteers who can offer one month?
Hope v9fs could be a help to distribute the task to
linux nodes.
--
next reply other threads:[~2005-08-02 0:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 0:46 YAMANASHI Takeshi [this message]
2005-08-02 1:37 ` arisawa
2005-08-02 4:00 ` Ronald G. Minnich
2005-08-02 5:41 ` arisawa
2005-08-02 14:07 ` Ronald G. Minnich
2005-08-04 11:59 ` arisawa
-- strict thread matches above, loose matches on Subject: below --
2005-08-01 12:30 YAMANASHI Takeshi
2005-08-01 13:51 ` Sergey Reva
2005-08-01 18:29 ` arisawa
2005-07-30 15:27 Sergey Reva
2005-07-31 1:28 ` arisawa
2005-08-01 16:51 ` Sergey Reva
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=f84728e25a2cc74ca06423ace4414326@orthanc.cc.titech.ac.jp \
--to=9.nashi@gmail.com \
--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).