From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Venti over DHT
Date: Tue, 20 Oct 2009 08:39:03 -0500 [thread overview]
Message-ID: <0642F742-829D-41C0-BE35-A4E8FEA49224@gmail.com> (raw)
In-Reply-To: <4ADDB2D7.3020606@metux.de>
On Oct 20, 2009, at 7:53 AM, Enrico Weigelt wrote:
>
> I've also done some bits of works in that area
> (nothing usable yet ;-o), but with different
> requirements:
>
> * storage near to the user (at least local mirrors)
> * equal data should get equal score (even w/ encryption)
> * automatic removal of stale blocks -> garbage collection
> * efficient also on small data blocks
>
> Especially the distributed GC together w/ encryption turned out
> not be quite trivial ;-o
> On the one hand we need things like timestamps, on the other hand
> we need to trace the tree structures w/o decryption.
>
> So I added several block types: eg. blob (payload data) and inode
> (holding the tree). blobs are encrypted w/ their score, thus
> reading takes scores (outer for retrieval, inner for decryption).
> inodes have an public area, listing just the outer scores and an
> encrypted one holding the inner scores. The tree formed by inodes
> doesn't necessarily has to be fully balanced, so incremental writes
> with special heuristics for preventing unncessary writes are possible.
>
>
> If someone likes to hear more about this, just let me know :)
>
I'm interested. Particularly in the multi-layer caching/mirroring and
the encryption/same-score details.
-eric
next prev parent reply other threads:[~2009-10-20 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 17:55 Roman Shaposhnik
2009-10-14 1:20 ` Russ Cox
[not found] ` <e763acc10910132148qbfd3a07q60d268a02d66c04e@mail.gmail.com>
2009-10-15 15:52 ` Roman Shaposhnik
2009-10-16 3:32 ` ron minnich
2009-10-16 4:03 ` Russ Cox
2009-10-20 12:53 ` Enrico Weigelt
2009-10-20 13:39 ` Eric Van Hensbergen [this message]
2009-10-21 11:53 ` Roman Shaposhnik
2009-10-29 19:13 ` Enrico Weigelt
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=0642F742-829D-41C0-BE35-A4E8FEA49224@gmail.com \
--to=ericvh@gmail.com \
--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).