From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /n/sources/contrib/
Date: Sun, 18 Nov 2007 00:08:10 -0500 [thread overview]
Message-ID: <475efbaa159da90890aaa976272045ee@quanstro.net> (raw)
In-Reply-To: <0cbda7d7e6f1a9e438a3b3cfc85c42ca@proxima.alt.za>
> That makes a lot of sense. How practical is it? At minimum, there
> would have to be a dedicated Venti to isolate "contrib" from other
> sections, plus the arenas would be large: not everyone has broadband
> access.
only the differences in the arenas would need to be copied. by definition,
the differences in the arenas are not bigger than the differences in the files.
bonus: you don't have to calculate the differences in the files.
this is something i am doing with ken's fs. i think the outline is the same
for venti. though given superblocks n, n+1 on the fs, one knows which
data to copy as superblocks are labeled by w address (block number).
the starting lba is waddr(n)*(RBUFSIZE/512) and you need to copy
(waddr(n+1)-waddr(n))/(RBUFSIZE/512) disk blocks.
not quite sure how that translates to venti.
- erik
next prev parent reply other threads:[~2007-11-18 5:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 5:35 lucio
2007-11-17 18:05 ` andrey mirtchovski
2007-11-17 18:55 ` lucio
2007-11-17 18:56 ` lucio
2007-11-17 22:00 ` erik quanstrom
2007-11-18 4:39 ` lucio
2007-11-18 5:08 ` erik quanstrom [this message]
2007-11-18 5:30 ` lucio
2007-11-18 10:25 ` johnny
2007-11-18 11:04 ` lucio
2007-11-18 11:33 ` roger peppe
2007-11-18 13:24 ` lucio
2007-11-18 14:18 ` erik quanstrom
2007-11-18 18:17 ` johnny
2007-11-19 16:29 ` roger peppe
2007-11-18 21:23 ` johnny
2007-11-17 18:13 ` Uriel
2007-11-17 18:58 ` lucio
2007-11-18 15:17 ` Russ Cox
2007-11-18 15:29 ` erik quanstrom
2007-11-18 18:26 ` Francisco J Ballesteros
2007-11-19 2:15 ` Russ Cox
2007-11-19 17:38 ` erik quanstrom
2007-11-19 17:53 ` Russ Cox
2014-05-23 7:20 David Hoskin
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=475efbaa159da90890aaa976272045ee@quanstro.net \
--to=quanstro@quanstro.net \
--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).