From: Francisco Ballesteros <nemo@lsub.org>
To: Russ Cox <rsc@swtch.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] reliability and failing over.
Date: Sat, 10 Sep 2005 01:16:40 +0200 [thread overview]
Message-ID: <600308d605090916167e4ea487@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a05090916064dad4060@mail.gmail.com>
Yep. I stand corrected. thanks.
But let's try first the simplest (unoptimized) version. If it
works well for real usage, I prefer a simpler (slower maybe) version.
On 9/10/05, Russ Cox <rsc@swtch.com> wrote:
> > Plan B usage shows that latency is the biggest problem.
> > I admit that only in unions, but if you join N different file servers
> > in a directory, and then you dup the latency, it may be a problem.
> > A workaround is just not to join too many servers, but it's a workaround,
> > not a fix.
>
> Of course, one could issue walks in parallel to all members
> of a union and then you'd get rid of this particular problem.
> And doing so would be easier in user space.
>
> Russ
>
next prev parent reply other threads:[~2005-09-09 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 20:55 [9fans] sept. town hall meeting Francisco Ballesteros
2005-09-09 21:05 ` Uriel
2005-09-09 22:10 ` [9fans] reliability and failing over Francisco Ballesteros
2005-09-09 22:24 ` Russ Cox
2005-09-09 22:50 ` Gorka guardiola
2005-09-09 23:02 ` Francisco Ballesteros
2005-09-09 23:06 ` Russ Cox
2005-09-09 23:16 ` Francisco Ballesteros [this message]
2005-09-10 13:11 ` Sape Mullender
2005-09-10 21:36 ` Francisco Ballesteros
2005-09-10 1:22 ` Eric Van Hensbergen
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=600308d605090916167e4ea487@mail.gmail.com \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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).