From: "'Bruce Fields'" <bfields@fieldses.org>
To: Frank Filz <ffilzlnx@mindspring.com>
Cc: "'Kernel NFS List'" <linux-nfs@vger.kernel.org>,
"'Ganesha NFS List'" <nfs-ganesha-devel@lists.sourceforge.net>
Subject: Re: pynfs updates
Date: Wed, 2 Oct 2013 07:36:07 -0400 [thread overview]
Message-ID: <20131002113607.GA7906@fieldses.org> (raw)
In-Reply-To: <00b801cebed9$312b6030$93822090$@mindspring.com>
On Tue, Oct 01, 2013 at 03:05:23PM -0400, Frank Filz wrote:
> > One more problem: CSID10 is failing against the Linux server with
> > NFS4ERR_TOO_MANY_OPS, because each of those lookups is actually a full
> > lookup from PUTROOTFH to /, resulting in 17 ops on my setup. Could we
> > maybe work relative to the parent directory instead?
>
> Ok, was able to fix this by doing a LOOKUP sequence in a separate compound
> followed by GETFH then in the compound that tests SAVEFH/RESTOREFH, just do
> PUTFH that saved FH.
>
> Things could be a lot smoother as discussed on IRC if the initialization
> stored away env.home_fh.
>
> Then with some work, this test could be simplified to:
>
> SEQUENCE, PUTFH(env.home_fh), OPEN, GETFH, SAVEFH, PUTFH(env.home_fh),
> RESTOREFH, CLOSE
>
> Note that that GETFH is not actually used by this test, but presumably
> open_create_op() would produce:
>
> PUTFH(env.home_fh), OPEN, GETFH
>
> Instead of what it currently does:
>
> PUTROOTFH, LOOKUP..., OPEN, GETFH
>
> The new branch is here:
>
> https://github.com/ffilz/pynfs/commits/master
Pulled, thanks!
--b.
next prev parent reply other threads:[~2013-10-02 11:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 18:17 pynfs updates Frank Filz
2013-09-30 22:11 ` Bruce Fields
2013-09-30 23:54 ` Frank Filz
2013-10-01 14:26 ` 'Bruce Fields'
2013-10-01 14:30 ` 'Bruce Fields'
2013-10-01 15:42 ` Frank Filz
2013-10-01 19:05 ` Frank Filz
2013-10-02 11:36 ` 'Bruce Fields' [this message]
2013-10-02 15:58 ` Frank Filz
2013-10-01 18:21 ` Frank Filz
2013-10-01 18:45 ` '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=20131002113607.GA7906@fieldses.org \
--to=bfields@fieldses.org \
--cc=ffilzlnx@mindspring.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfs-ganesha-devel@lists.sourceforge.net \
/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).