From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benny Halevy Subject: Re: [pnfs] pnfs code structure Date: Thu, 27 May 2010 20:58:13 +0300 Message-ID: <4BFEB2B5.3050006@panasas.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from daytona.panasas.com ([67.152.220.89]:22072 "EHLO daytona.int.panasas.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753843Ab0E0R6R (ORCPT ); Thu, 27 May 2010 13:58:17 -0400 In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: quanli gui Cc: linux-ide@vger.kernel.org Hi, [please note that the old pnfs@linux-nfs.org mailing list is deprecated and we moved our pnfs discussions to linux-nfs@vger.kernel.org] I have very rough and informal design notes I took not too long ago: http://linux-nfs.org/pipermail/pnfs/attachments/20100304/f90bede4/attachment.txt That said, I hope the code is clear enough to browse and get what it does. What do you mean by "replication policy for the pnfs"? Benny On May. 27, 2010, 4:22 +0300, quanli gui wrote: > Our group want to experiment something on the pnfs, for example, the > replication policy for the pnfs,and so on. So we want something about > the pnfs development, for example, the pnfs code structure, the key data > structure for the pnfs. Who has the related things? Please help us. > > > > _______________________________________________ > NOTE: THIS LIST IS DEPRECATED. Please use linux-nfs@vger.kernel.org > instead. (To subscribe to linux-nfs@vger.kernel.org: send "subscribe > linux-nfs" in the body of a message to majordomo@vger.kernel.org.) > > pNFS mailing list > pNFS@linux-nfs.org > http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs