From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: Design challenges in chunkd self-checking
Date: Tue, 22 Dec 2009 18:40:14 -0700
Message-ID: <20091222184014.22c5d1c5@redhat.com>
References: <20091222144111.789a5b91@redhat.com>
	<4B314BAE.4010805@garzik.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <hail-devel-owner@vger.kernel.org>
In-Reply-To: <4B314BAE.4010805@garzik.org>
Sender: hail-devel-owner@vger.kernel.org
List-ID: <hail-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail List <hail-devel@vger.kernel.org>

On Tue, 22 Dec 2009 17:43:58 -0500
Jeff Garzik <jeff@garzik.org> wrote:

> It is normal and reasonable to maintain global information about all 
> in-progress operations.  Caching systems do that, for example, to ensure 
> multiple cache requests for object A do not initiate multiple 
> simultaneous back-end requests for object A.

Unfortunately, this requires a data structure that permits searching.
Since I lack the classical CS education, I cannot select an appropriate
structure beyond "double-linked list and a hope that we'll never see
more than 10 simultaneous I/Os".

-- Pete