From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [Patch 1/2] tabled: fix bugs in streaming of data
Date: Thu, 7 Jan 2010 15:27:16 -0700 [thread overview]
Message-ID: <20100107152716.34b769bc@redhat.com> (raw)
In-Reply-To: <4B465BE9.1060506@garzik.org>
On Thu, 07 Jan 2010 17:10:49 -0500
Jeff Garzik <jeff@garzik.org> wrote:
> 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.
At least 1 of the 3 that I fixed definitely was a corruption that I introduced
to your design when I adapted it to simultaneous streaming on write.
Not sure about other two, but maybe I just screwed tabled.
But sure, if you have a moment to re-check chunkd, be my guest.
-- Pete
prev parent reply other threads:[~2010-01-07 22:27 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
2010-01-07 22:27 ` Pete Zaitcev [this message]
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=20100107152716.34b769bc@redhat.com \
--to=zaitcev@redhat.com \
--cc=hail-devel@vger.kernel.org \
--cc=jeff@garzik.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.