Message-ID: <4E9E2A4A.2060107@tonian.com>
Date: Tue, 18 Oct 2011 18:39:22 -0700
From: Benny Halevy <bhalevy@tonian.com>
MIME-Version: 1.0
To: "J. Bruce Fields" <bfields@redhat.com>
CC: NFS list <linux-nfs@vger.kernel.org>
Subject: Re: linux-pnfs pnfs-all-3.1-rc10-2011-10-18
References: <4E9E1A2C.6090807@tonian.com> <20111019005042.GA14789@pad.fieldses.org>
In-Reply-To: <20111019005042.GA14789@pad.fieldses.org>
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-nfs-owner@vger.kernel.org

On 2011-10-18 17:50, J. Bruce Fields wrote:
> 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?

yes.

> 
> 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?
> 

Yes, basically.
Eventually, this needs to work with the infamous back-end protocol
to enforce client fencing.

Benny

>> 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.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html