From: Benny Halevy <bhalevy@panasas.com>
To: quanli gui <gqlxj1987@gmail.com>
Cc: linux-pnfs <linux-nfs@vger.kernel.org>
Subject: Re: [pnfs] pnfs code structure
Date: Tue, 01 Jun 2010 06:38:02 +0300 [thread overview]
Message-ID: <4C04809A.1000503@panasas.com> (raw)
In-Reply-To: <AANLkTinMn17Fwkd_mVSSWnTUc1mT5pjWNZPoajbab07T-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On May. 28, 2010, 5:55 +0300, quanli gui <gqlxj1987@gmail.com> wrote:
> the replication policy for the pnfs is that we want add some replication
> to the pnfs, to improve the performance of the pnfs, which is mentioned
> in the pnfs white-paper.
OK. For that, multiple copies of the data should be maintained.
The way to do it is different for each layout type.
Benny
>
> 2010/5/28 Benny Halevy <bhalevy@panasas.com <mailto:bhalevy@panasas.com>>
>
> Hi,
>
> [please note that the old pnfs@linux-nfs.org
> <mailto:pnfs@linux-nfs.org> mailing list is deprecated
> and we moved our pnfs discussions to linux-nfs@vger.kernel.org
> <mailto: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 <gqlxj1987@gmail.com
> <mailto:gqlxj1987@gmail.com>> 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 <mailto:linux-nfs@vger.kernel.org>
> > instead. (To subscribe to linux-nfs@vger.kernel.org
> <mailto:linux-nfs@vger.kernel.org>: send "subscribe
> > linux-nfs" in the body of a message to majordomo@vger.kernel.org
> <mailto:majordomo@vger.kernel.org>.)
> >
> > pNFS mailing list
> > pNFS@linux-nfs.org <mailto:pNFS@linux-nfs.org>
> > http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
>
>
prev parent reply other threads:[~2010-06-01 3:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTilqCahXkLmgu0EL0Vbje_VcH0msM5o5I2edGglG@mail.gmail.com>
2010-05-27 17:58 ` [pnfs] pnfs code structure Benny Halevy
[not found] ` <AANLkTinMn17Fwkd_mVSSWnTUc1mT5pjWNZPoajbab07T@mail.gmail.com>
[not found] ` <AANLkTinMn17Fwkd_mVSSWnTUc1mT5pjWNZPoajbab07T-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-01 3:38 ` Benny Halevy [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=4C04809A.1000503@panasas.com \
--to=bhalevy@panasas.com \
--cc=gqlxj1987@gmail.com \
--cc=linux-nfs@vger.kernel.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.