From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Regarding venti block size
Date: Mon, 16 Feb 2009 09:03:54 -0800 [thread overview]
Message-ID: <dd6fe68a0902160903o74a45d3eha973cb768b64927a@mail.gmail.com> (raw)
In-Reply-To: <63884bcf-d00e-470e-b931-7e5be3f7bce8@g38g2000yqd.googlegroups.com>
> The problem is that I was planning on keeping the number of parts is
> fixed. So depending on the file size, the part size will vary. And
> therefore sometimes the (part block) that I store will be more than
> the current upper limit of 64k.
>
> It would be great if you could let me know your thoughts on this.
I think you will need to rewrite both venti and the
venti protocol to get around the 64k limit.
I started to do this once and decided it was
too large a change to bother. If you don't care
about coalescing duplicate blocks (and you
don't seem to), why not use an extent-based
file system instead?
Russ
next prev parent reply other threads:[~2009-02-16 17:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 10:25 anooop.anooop
2009-02-16 11:52 ` matt
2009-02-16 14:16 ` erik quanstrom
2009-02-16 14:20 ` erik quanstrom
2009-02-16 15:56 ` anooop.anooop
2009-02-16 16:17 ` matt
2009-02-16 17:03 ` Russ Cox [this message]
2009-02-16 17:11 ` erik quanstrom
2009-02-16 17:17 ` roger peppe
2009-02-16 17:28 ` anooop.anooop
2009-02-16 19:08 ` lucio
2009-02-16 19:24 ` ron minnich
2009-02-17 9:53 ` anooop.anooop
2009-02-17 0:17 ` matt
2009-02-17 9:53 ` anooop.anooop
[not found] ` <2c60577b-edf1-4f3c-bdd9-d8b1b2859a5b@x38g2000yqj.googlegroups.co>
2009-02-17 13:38 ` erik quanstrom
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=dd6fe68a0902160903o74a45d3eha973cb768b64927a@mail.gmail.com \
--to=rsc@swtch.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).