So this logic is already in V2.4-dev-20 for FSAL_GPFS ?
Marc.
From: Daniel Gryniewicz <[email protected]>
To: Marc Eshel/Almaden/IBM@IBMUS, Frank Filz <[email protected]>
Cc: "'nfs-ganesha-devel'" <[email protected]>
Date: 06/09/2016 12:02 PM
Subject: Re: [Nfs-ganesha-devel] Posted patches that include my
continuation of Dan's work on removing the attrlist from fsal_obj_handle
On 06/09/2016 02:25 PM, Marc Eshel wrote:
> Hi Frank,
> I was not following of the recent changes to Ganesha and I understand
> that they are not complete but I just want to make sure we don't break
it.
> What I see is that the recent version is that fh passed on the up call
> is used as the actual fh to do delegation call back, but up call was not
> passing a full fh it is passing a key that the old code used to use for
> a look-up of the full fh in the cache_entry_t and used that full fh to
> recall delegation from the NFS client.
> Am I missing something?
> Thanks, Marc.
>
>
All the up-calls take a handle key that is passed to create_handle().
In the cached case, MDCACHE will look up the cached handle in
create_handle(), so everything should be working correctly. No actual
fsal_handle objects are passed up the chain in any of the up-calls.
Daniel
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Nfs-ganesha-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
