public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: andros@netapp.com
To: bfields@fieldses.org
Cc: pnfs@linux-nfs.org, linux-nfs@vger.kernel.org,
	Andy Adamson <andros@netapp.com>
Subject: [PATCH 1/1] pynfs: set cache_this to false for readdir
Date: Tue, 28 Apr 2009 12:56:15 -0400	[thread overview]
Message-ID: <1240937775-23746-2-git-send-email-andros@netapp.com> (raw)
In-Reply-To: <1240937775-23746-1-git-send-email-andros@netapp.com>

From: Andy Adamson <andros@netapp.com>

testserver.py was failing initialization against the new Linux server DRC
which has a lower max resonse size cached value than the initializaion
readdir response.

Set cache_this to False

Signed-off-by: Andy Adamson <andros@netapp.com>
---
 nfs4.1/server41tests/environment.py |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/nfs4.1/server41tests/environment.py b/nfs4.1/server41tests/environment.py
index fb0e7ed..8623158 100644
--- a/nfs4.1/server41tests/environment.py
+++ b/nfs4.1/server41tests/environment.py
@@ -415,7 +415,7 @@ def do_readdir(sess, file, cookie=0, cookieverf='', attrs=0L,
     baseops = use_obj(file)
     while True:
         readdir_op = op.readdir(cookie, cookieverf, dircount, maxcount, attrs)
-        res = sess.compound(baseops + [readdir_op])
+        res = sess.compound(baseops + [readdir_op], cache_this=False)
         check(res, msg="READDIR with cookie=%i, maxcount=%i" % (cookie, maxcount))
         reply = res.resarray[-1].reply
         if not reply.entries and not reply.eof:
-- 
1.5.4.3


  reply	other threads:[~2009-04-28 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 16:56 [PATCH 0/29] NFSv4.1 Server DRC rewrite Version 2 andros
2009-04-28 16:56 ` andros [this message]
2009-05-15 22:46 ` J. Bruce Fields
2009-05-16  8:16   ` 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=1240937775-23746-2-git-send-email-andros@netapp.com \
    --to=andros@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=pnfs@linux-nfs.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