From: "J. Bruce Fields" <bfields@fieldses.org>
To: James Lentini <jlentini@netapp.com>
Cc: Thomas Talpey <talpey@netapp.com>,
Tom Tucker <tom@opengridcomputing.com>,
general-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org,
linux-nfs@vger.kernel.org
Subject: Re: new NFS/RDMA instructions for 2.6.25-rc1
Date: Mon, 11 Feb 2008 16:00:44 -0500 [thread overview]
Message-ID: <20080211210044.GA4561@fieldses.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0802111552080.23589-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
On Mon, Feb 11, 2008 at 03:56:17PM -0500, James Lentini wrote:
>
>
> On Mon, 11 Feb 2008, J. Bruce Fields wrote:
>
> > On Mon, Feb 11, 2008 at 12:25:14PM -0500, James Lentini wrote:
> > >
> > > Linux 2.6.25 will be the first official kernel release to contain the
> > > NFS/RDMA server. With the client and server now both available in
> > > 2.6.25-rc1, we've simplified our NFS/RDMA installation instructions.
> > > The new instructions are available here:
> > >
> > > http://nfs-rdma.sourceforge.net/Documents/README
> >
> > Any reason not to add that to the linux tree, say in
> > Documentation/filesystems/nfs-rdma.txt?
> >
> > --b.
>
> That sounds like a good idea Bruce. The current document is strictly a
> HOWTO. Should we add sections on the design and implementation?
Sure, that'd be great. But I think it'd be fine to submit the howto
pretty much as it is and add the rest later.
--b.
next prev parent reply other threads:[~2008-02-11 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 17:25 [ofa-general] new NFS/RDMA instructions for 2.6.25-rc1 James Lentini
[not found] ` <Pine.LNX.4.64.0802111223040.23589-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
2008-02-11 17:33 ` J. Bruce Fields
2008-02-11 20:56 ` [ofa-general] " James Lentini
[not found] ` <Pine.LNX.4.64.0802111552080.23589-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
2008-02-11 21:00 ` J. Bruce Fields [this message]
2008-02-25 16:49 ` James Lentini
[not found] ` <Pine.LNX.4.64.0802251140290.16537-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
2008-02-25 17:04 ` [ofa-general] " Roland Dreier
[not found] ` <ada7igt2cjf.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2008-02-25 17:20 ` James Lentini
[not found] ` <Pine.LNX.4.64.0802251214550.16537-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
2008-02-25 18:12 ` J. Bruce Fields
2008-02-25 18:15 ` James Lentini
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=20080211210044.GA4561@fieldses.org \
--to=bfields@fieldses.org \
--cc=general-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=jlentini@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=talpey@netapp.com \
--cc=tom@opengridcomputing.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox