Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Fredric Isaman <iisaman@citi.umich.edu>
Cc: NFS list <linux-nfs@vger.kernel.org>
Subject: Re: pynfs and server attributes?
Date: Mon, 10 Dec 2007 17:19:19 -0500	[thread overview]
Message-ID: <475DBB67.4030001@garzik.org> (raw)
In-Reply-To: <Pine.BSO.4.64.0712101633470.15300@citi.umich.edu>

Fredric Isaman wrote:
> On Mon, 10 Dec 2007, Jeff Garzik wrote:
> 
>> Is there a pynfs list somewhere?
>>
> 
> Not that I know of.
> 
> 
>> The pynfs tests for too-long strings, too-long reads and writes do not 
>> seem to take into account maxname, maxread and maxwrite attributes.
>>
>> I actually have to _increase_ the python "longname" test variable in 
>> order for the test to behave properly on my server :)
>>
>>     Jeff
> 
> 
> The fixed (but easily changeable) "longname" was intentional in order to 
> avoid test dependencies on GETATTR, and non-mandatory attributes at that.
> 
> Would making the length of longname a command line option be useful?


Definitely.  That, and the max-read and max-write attributes.

There is at least one test that issues a WARNING when my server returns 
128k (its max read size) rather than the requested 9000000 count.

I have not investigated that yet, but I was sorta assuming that my 
server was behaving correctly in that case.

	Jeff




      reply	other threads:[~2007-12-10 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 21:30 pynfs and server attributes? Jeff Garzik
2007-12-10 21:45 ` Fredric Isaman
2007-12-10 22:19   ` Jeff Garzik [this message]

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=475DBB67.4030001@garzik.org \
    --to=jeff@garzik.org \
    --cc=iisaman@citi.umich.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