From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [Patch 1/2] tabled: fix bugs in streaming of data
Date: Thu, 07 Jan 2010 17:10:49 -0500 [thread overview]
Message-ID: <4B465BE9.1060506@garzik.org> (raw)
In-Reply-To: <20100105210255.74397f8c@redhat.com>
On 01/05/2010 11:02 PM, Pete Zaitcev wrote:
> On Tue, 05 Jan 2010 04:13:36 -0500
> Jeff Garzik<jeff@garzik.org> wrote:
>
>> applied... chunkd needs these fixes also, yes?
>
> No, it appears correct as-is. Although, the large-object test in
> the suite does not check the data it transmits, so if chunkd were
> broken, we might not know it. On the other hand, the fact that
> tabled stores test objects in chunkservers assures us that it
> works at least as far as tabled's tests verify.
I was thinking specifically that chunkd may want the in-progress xfer
codes changes in your patch. chunkd, tabled, nfs4d (and ancient
storaged) all share the same basic write-in-progress and TCP data xfer code.
I'll take a look, no need to worry about it yourself.
Jeff
next prev parent reply other threads:[~2010-01-07 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 7:27 [Patch 1/2] tabled: fix bugs in streaming of data Pete Zaitcev
2010-01-05 9:13 ` Jeff Garzik
2010-01-06 4:02 ` Pete Zaitcev
2010-01-07 22:10 ` Jeff Garzik [this message]
2010-01-07 22:27 ` Pete Zaitcev
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=4B465BE9.1060506@garzik.org \
--to=jeff@garzik.org \
--cc=hail-devel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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.