All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Benny Halevy <benny@tonian.com>, NFS list <linux-nfs@vger.kernel.org>
Subject: Final disposition of the pNFSD tree
Date: Tue, 25 Oct 2011 20:26:56 -0700	[thread overview]
Message-ID: <4EA77E00.6090002@panasas.com> (raw)

Benny what is the state of the PNFSD tree? Can you sign on it's stability for
a large scale testing or should I be using the nfsd-3.1 based tree?

As far as I could see. The last tree that did not have nfsd-3.2 
new state patches was pnfs-all-3.1-rc8-2011-10-06.

pnfs-all-3.1-rc9-2011-10-17 Had some of them, but I guess not the major
ones. (Should I test with this one?)

And pnfs-all-3.1-rc10-2011-10-18 (pnfs/pnfs-all-latest) has all of them.
Is it stable?

My last heavy testing was actually on pnfs-all-3.1-rc6-2011-09-20. If I diff
that with pnfs-all-3.1-rc8-2011-10-06 on fs/nfsd/ I can still see huge amount
of for-nfsd-v3.2 changes. I know you have found some bugs, So I guess I'll stick
with the v3.1-rc6-pnfs based tree for the Server and v3.1 release Kernel + ore-v3.2
patches.

Do you think you will release a 3.1 based pnfs tree that is completely based on
the v3.1-nfsd version and the old pnfs tree, without any for-v3.2-pnfsd patches?

Thanks
Boaz

             reply	other threads:[~2011-10-26  3:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26  3:26 Boaz Harrosh [this message]
2011-10-26  5:25 ` Final disposition of the pNFSD tree Benny Halevy
2011-10-31 17:12   ` Benny Halevy

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=4EA77E00.6090002@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=benny@tonian.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.