9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] file server speed
Date: Thu, 17 Jul 2014 15:10:34 -0400	[thread overview]
Message-ID: <fd1c3cf7f156332dcd23891262f87059@ladd.quanstro.net> (raw)
In-Reply-To: <20140717190129.81607B827@mail.bitblocks.com>

> So long as a server returns a block corresponding to its SHA1
> score, you (the client) don't care whether it is the same
> server you wrote the original block to or another (and you can
> always verify the returned block). This opens up some

but this isn't unique to content-addressed storage.  as long
as the block contents are the same, normal block storage can
be served from anywhere.

> interesting choices. For instance, you can multicast each read
> or write or you can set up a hierarchy of servers and switch
> to another one (or even get different blocks from different
> instances). How the writes are handled/replicated.stored is
> entirely upto the server (cluster).  Or you can implement a
> bittorrent like facility on top of venti (I call it bitventi
> or b20).

why not distributed hashing?  distributed hashes have existing
fast implementations.  venti does not.

- erik



  reply	other threads:[~2014-07-17 19:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15  6:13 kokamoto
2014-07-15 13:02 ` Anthony Sorace
2014-07-15 16:30 ` cinap_lenrek
2014-07-15 16:56   ` erik quanstrom
2014-07-16  0:04   ` kokamoto
2014-07-16  0:36     ` kokamoto
2014-07-16 17:26       ` erik quanstrom
2014-07-16 14:23     ` Steven Stallion
2014-07-16 14:53       ` Ramakrishnan Muthukrishnan
2014-07-17  1:13         ` Steven Stallion
2014-07-17 17:13           ` Ramakrishnan Muthukrishnan
2014-07-17 21:44         ` cam
2014-07-16 17:41       ` erik quanstrom
2014-07-16 23:15       ` kokamoto
2014-07-17  0:29         ` Steven Stallion
2014-07-17  0:31           ` Steven Stallion
2014-07-17  1:10             ` john francis lee
2014-07-17  1:09           ` john francis lee
2014-07-17  1:10           ` Bakul Shah
2014-07-17 16:56           ` erik quanstrom
2014-07-17 18:14             ` Bakul Shah
2014-07-17 18:39               ` erik quanstrom
2014-07-17 19:01               ` Bakul Shah
2014-07-17 19:10                 ` erik quanstrom [this message]
2014-07-17 19:26                   ` Bakul Shah
2014-07-16 17:23     ` erik quanstrom
2014-07-16 23:01       ` kokamoto
2014-07-17 17:03         ` erik quanstrom
2014-07-18 16:50           ` hiro
2014-07-18 19:36             ` erik quanstrom
2014-07-18 20:11               ` Bakul Shah

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=fd1c3cf7f156332dcd23891262f87059@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).