From: Jeff Garzik <jeff@garzik.org>
To: hail-devel@vger.kernel.org
Subject: [PATCH 0/3] update chunkd checksum verification scheme
Date: Thu, 15 Jul 2010 14:18:57 -0400 [thread overview]
Message-ID: <20100715181857.GA16632@havoc.gtf.org> (raw)
This patchset is part of the work necessary to get ranged-GET (aka
partial GET) working. As explained in
http://marc.info/?l=hail-devel&m=127871407125539&w=2 the current chunkd
checksum scheme does not work at all for partial retrievals, and must be
revamped.
These patches present step 1 of 4, adding a table of checksums to
chunkd's local on-disk format.
There are no protocol or API changes in this patchset, existing clients
should work fine without any changes.
Nevertheless, this will not be committed to the main branch until
partial retrieval is actually implemented. I don't commit changes
unless they are actually neeeded. This checksum table and sendfile
removal work is not required until partial-GET actually exists.
Jeff
next reply other threads:[~2010-07-15 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 18:18 Jeff Garzik [this message]
2010-07-15 18:20 ` [PATCH 1/3] chunkd: remove sendfile(2) support Jeff Garzik
2010-07-15 18:20 ` [PATCH 2/3] chunkd: pass data-length to PUT backend init Jeff Garzik
2010-07-15 18:21 ` [PATCH 3/3] chunkd: on-disk format stores per-64k checksums Jeff Garzik
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=20100715181857.GA16632@havoc.gtf.org \
--to=jeff@garzik.org \
--cc=hail-devel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.