Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@redhat.com>
To: Benny Halevy <bhalevy@tonian.com>
Cc: NFS list <linux-nfs@vger.kernel.org>
Subject: Re: linux-pnfs pnfs-all-3.1-rc10-2011-10-18
Date: Tue, 18 Oct 2011 20:50:43 -0400	[thread overview]
Message-ID: <20111019005042.GA14789@pad.fieldses.org> (raw)
In-Reply-To: <4E9E1A2C.6090807@tonian.com>

On Tue, Oct 18, 2011 at 05:30:36PM -0700, Benny Halevy wrote:
> DS stateids are still tracked in a global hash table (as they are
> generated by the MDS)

By DS stateid's you're talking about stateid's that a DS receives on IO?

I hadn't thought about those....

Does the DS need to do anything with them other than look them up and
make a binary OK vs. BAD_STATEID decision?

> I also seized the opportunity to clean up the pnfs patch series.
> white space, use of inline, etc.  no functional changes otherwise.
> 
> Tested to pass the connectathon tests over pnfsd-lexp.

Thanks!

--b.

  reply	other threads:[~2011-10-19  0:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19  0:30 linux-pnfs pnfs-all-3.1-rc10-2011-10-18 Benny Halevy
2011-10-19  0:50 ` J. Bruce Fields [this message]
2011-10-19  1:39   ` 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=20111019005042.GA14789@pad.fieldses.org \
    --to=bfields@redhat.com \
    --cc=bhalevy@tonian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox