That really helped. Much appreciated Frank. -Sagar
On Wed, Sep 7, 2016 at 7:01 PM, Frank Filz <ffilz...@mindspring.com> wrote: > Owner is an opaque value to the FSAL. It happens to be the pointer to a > state_lock_owner_t so Ganesha does expect it back on call backs when async > blocking locks are supported (see other e-mail chain for issues that are > arising without that support). Ganesha never dereferences the owner value > from the FSAL however, it just searches its blocked locks list for locks > with the same owner. > > > > The FSAL may use it in any way it chooses to differentiate lock owners. > > > > I should note that all new FSAL development should use the support_ex API, > where there will be a state_t object for each lock owner/file pair. This > actually allows the FSAL to define it’s own lock owner in whatever way > makes sense (but the opaque void * lock owner is also still available). > > > > I hope that helps, > > > > Frank > > > > *From:* Sagar M D [mailto:sagar...@gmail.com] > *Sent:* Wednesday, September 7, 2016 3:37 PM > *To:* nfs-ganesha-devel@lists.sourceforge.net > *Subject:* [Nfs-ganesha-devel] lock_op > > > > Hi All, > > > > could someone please shed light on the usage of "owner" in fsal side ? Is > "owner" implemented as comments says "it is not yet". > > > > Also "owner" looks opaque to FSAL. Will NFS-Ganesha expects this back in > any call ? > > > > how fsal should use this "owner" ? > > > > /** > > * @brief Perform a lock operation > > * > > * This function performs a lock operation (lock, unlock, test) on a > > * file. > > * > > * @param[in] obj_hdl File on which to operate > > * @param[in] owner Lock owner (Not yet implemented) > > * @param[in] lock_op Operation to perform > > * @param[in] request_lock Lock to take/release/test > > > > * @param[out] conflicting_lock Conflicting lock > > * > > * @return FSAL status. > > */ > > fsal_status_t (*lock_op)(struct fsal_obj_handle *obj_hdl, > > void *owner, > > fsal_lock_op_t lock_op, > > fsal_lock_param_t *request_lock, > > fsal_lock_param_t *conflicting_lock); > > > > Thanks, > > Sagar > > > ------------------------------ > [image: Avast logo] <https://www.avast.com/antivirus> > > This email has been checked for viruses by Avast antivirus software. > www.avast.com <https://www.avast.com/antivirus> > >
------------------------------------------------------------------------------
_______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
