hail-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: hail-devel@vger.kernel.org
Subject: [PATCH 0/3 v2] chunkd on-disk checksumming
Date: Sat, 17 Jul 2010 01:46:16 -0400	[thread overview]
Message-ID: <20100717054616.GA9993@havoc.gtf.org> (raw)


This patchset is rediffed and bug-fixed from previous posting.  Patches
are against hail.git commit 68f68e3630cae4bb2ca651b577c1d4d0292687b1.

See original posting for more info:
http://marc.info/?l=hail-devel&m=127921794109300&w=2

             reply	other threads:[~2010-07-17  5:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-17  5:46 Jeff Garzik [this message]
2010-07-17  5:46 ` [PATCH 1/3 v2] chunkd: remove sendfile(2) zero-copy support Jeff Garzik
2010-07-18  3:45   ` Steven Dake
2010-07-18 23:10     ` Jeff Garzik
2010-07-18 23:23       ` Jeff Garzik
2010-07-17  5:47 ` [PATCH 2/3 v2] chunkd: Add checksum table to on-disk format, one sum per 64k of data Jeff Garzik
2010-07-17  5:47 ` [PATCH 3/3 v2] [chunkd] match network buffer size to checksum buffer size (64k) Jeff Garzik
2010-07-18  7:09 ` [PATCH 4/4] chunkd checksums each block, as it is read from disk 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=20100717054616.GA9993@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).