From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "Schumaker, Bryan" <Bryan.Schumaker@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: readdir cookies
Date: Mon, 17 Sep 2012 12:51:26 -0400 [thread overview]
Message-ID: <20120917165126.GL30673@fieldses.org> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA908FC8D4C@SACEXCMBX04-PRD.hq.netapp.com>
On Mon, Sep 17, 2012 at 04:05:10PM +0000, Myklebust, Trond wrote:
> > -----Original Message-----
> > From: linux-nfs-owner@vger.kernel.org [mailto:linux-nfs-
> > owner@vger.kernel.org] On Behalf Of J. Bruce Fields
> > Sent: Monday, September 17, 2012 11:54 AM
> > To: Myklebust, Trond; Schumaker, Bryan
> > Cc: linux-nfs@vger.kernel.org
> > Subject: readdir cookies
> >
> > How does the nfs client decide what directory cookies to return? (As the
> > d_off field to readdir, for example).
> >
> > I'd assumed it would return the server's cookie, but testing shows it returns a
> > simple integer sequence.
>
> We cache the cookies and use them to figure out where the readdir cursor is after a directory update, but we use positive integers for telldir()/seekdir(). The reason is that too many servers return cookies that use > 32 bits (NFSv2-incompatible) or are unsigned.
Ok--so the tradeoff is that telldir/seekdir cookies may not be good
indefinitely?
--b.
next prev parent reply other threads:[~2012-09-17 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 15:54 readdir cookies J. Bruce Fields
2012-09-17 16:05 ` Myklebust, Trond
2012-09-17 16:51 ` J. Bruce Fields [this message]
2012-09-17 16:56 ` Myklebust, Trond
2012-09-17 17:50 ` J. Bruce Fields
2012-09-17 18:03 ` Myklebust, Trond
2012-09-17 19:53 ` 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=20120917165126.GL30673@fieldses.org \
--to=bfields@fieldses.org \
--cc=Bryan.Schumaker@netapp.com \
--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.