From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: Design challenges in chunkd self-checking
Date: Tue, 5 Jan 2010 13:47:02 -0700 [thread overview]
Message-ID: <20100105134702.1e72ced2@redhat.com> (raw)
In-Reply-To: <4B319030.9070906@garzik.org>
On Tue, 22 Dec 2009 22:36:16 -0500
Jeff Garzik <jeff@garzik.org> wrote:
> Seems like a mutex-wrapped GLib hash table would work...
I dunno about this... See, I think it's like kernel timers: there's a
lot of premium on having add and remove quick, and the rest is whatever.
The important part is not to penalize the latency of normal requests
only to make self-checking faster. That process takes hours to loop
anyway, maybe days.
I went with a list for now.
-- Pete
next prev parent reply other threads:[~2010-01-05 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 21:41 Design challenges in chunkd self-checking Pete Zaitcev
2009-12-22 22:43 ` Jeff Garzik
2009-12-23 1:40 ` Pete Zaitcev
2009-12-23 3:36 ` Jeff Garzik
2010-01-05 20:47 ` Pete Zaitcev [this message]
2010-01-05 21:02 ` Jeff Garzik
2010-01-05 21:39 ` Pete Zaitcev
2010-01-05 21:53 ` Jeff Garzik
2010-01-05 22:10 ` 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=20100105134702.1e72ced2@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.