From: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
To: NFS list <linux-nfs@vger.kernel.org>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: nfsv4 + readdir == too many requests
Date: Thu, 13 Jan 2011 22:14:37 +0100 [thread overview]
Message-ID: <4D2F6B3D.7080007@desy.de> (raw)
In-Reply-To: <1294952462.3038.29.camel@heimdal.trondhjem.org>
On 01/13/2011 10:01 PM, Trond Myklebust wrote:
> On Thu, 2011-01-13 at 21:26 +0100, Tigran Mkrtchyan wrote:
>
>> By running intensive tests I notice that readdir oration over nfsv4.1
>> asks for
>> file attributes in readdir (attr_request) and later on for each file. To
>> me it looks like
>> broken.
>>
>> This 2.6.37 + pnfs-all-latests :
>>
>> git://linux-nfs.org/~bhalevy/linux-pnfs.git
>> 378978453b64bf895de8cd0e68dbcd9e9c0155ce
>>
>> 100% reproducible.
>>
> 1) What makes you think this is broken, and not just a case of the
> attribute cache timing out and/or the directory changing?
>
The directory does not changed. I issue 'ls -l' and with wireshak can
see READDIR requests
followed by GETATTR. looks like cache is ignored or too small.
> 2) Can you produce a testcase that proves brokenness?
>
I will try to come up with something.
> 3) Can you reproduce on a non-pnfs-all-latests kernel?
>
> Readdir shouldn't be affected by the stuff in Benny's tree, but I'm
> always wary of tests on out-of-mainline trees.
>
NP. with vanilla 2.6.37 ?
Regards,
Tigran.
> Cheers
> Trond
>
next prev parent reply other threads:[~2011-01-13 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 20:26 nfsv4 + readdir == too many requests Tigran Mkrtchyan
2011-01-13 21:01 ` Trond Myklebust
2011-01-13 21:14 ` Tigran Mkrtchyan [this message]
2011-01-17 15:39 ` Tigran Mkrtchyan
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=4D2F6B3D.7080007@desy.de \
--to=tigran.mkrtchyan@desy.de \
--cc=Trond.Myklebust@netapp.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.