From: Boaz Harrosh <bharrosh@panasas.com>
To: Gregory Magoon <gmagoon@MIT.EDU>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
<linux-nfs@vger.kernel.org>
Subject: Re: NFSv4 vs NFSv3 with MPICH2-1.4
Date: Thu, 28 Jul 2011 15:31:18 -0700 [thread overview]
Message-ID: <4E31E336.9090702@panasas.com> (raw)
In-Reply-To: <20110728180120.bf6gq5zyos8wwg4s@webmail.mit.edu>
On 07/28/2011 03:01 PM, Gregory Magoon wrote:
> I'll try this the next time I get a chance.
>
> Just to be clear, I don't think it is a performance issue; I think it is just
> getting stuck.
>
> Greg
>
> Quoting Trond Myklebust <Trond.Myklebust@netapp.com>:
>
>
>> Have you turned off delegations on the server? I wouldn't expect them to
>> help much on an MPI workload.
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Gregory
We are using MPICH2-1.3.1 and the IOR mpich test. as well as the mdtest
test. And have had no issues so far with nfsv4 nfsv4.1 and pnfs. In fact
this is our standard performance test.
What tests are you using?
Do you know of any major changes between MPICH2-1.3.1 and MPICH2-1.4?
Also are you using the builtin nfs-client driver or the POSIX interface?
Boaz
next prev parent reply other threads:[~2011-07-28 22:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 19:23 NFSv4 vs NFSv3 with MPICH2-1.4 Gregory Magoon
2011-07-28 20:58 ` Trond Myklebust
2011-07-28 21:24 ` Gregory Magoon
2011-07-28 21:47 ` Trond Myklebust
2011-07-28 22:01 ` Gregory Magoon
2011-07-28 22:31 ` Boaz Harrosh [this message]
2011-07-28 23:15 ` Gregory Magoon
2011-07-30 3:19 ` Boaz Harrosh
2011-07-30 3:56 ` Loewe, Bill
2011-08-02 16:19 ` Gregory Magoon
2011-08-09 23:15 ` Gregory Magoon
2011-08-10 0:54 ` Boaz Harrosh
2011-07-29 14:51 ` J. Bruce Fields
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=4E31E336.9090702@panasas.com \
--to=bharrosh@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=gmagoon@MIT.EDU \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).