I see. That makes sense. I think in most case the file open delegation will be enough. It seems to me that the directory data is at least as critical as the file meta data such as file attributes. This kind of data, in most cases, should be propagated to the server as soon as possible. Not sure whether this argument makes sense. :P Thanks! best, Yudong On Wed, Aug 4, 2010 at 2:09 PM, Trond Myklebust <trond.myklebust@xxxxxxxxxx> wrote: > On Wed, 2010-08-04 at 12:21 -0700, Yudong Gao wrote: >> Hi, >> >> I am not able to find the implementation of directory delegation, >> either. Similarly, the callback functions CB_NOTIFY is not >> implemented, either. I find that in preprocss_nfs41_op() in >> callback_xdr.c, whenever a CB_NOTIFY is encountered, an >> NFS4ERR_NOTSUPP is returned directly. >> >> Am I missing something? Or they are just not supported in the current version? > > The client currently does not request any directory delegations or > notifications, so there is no reason for it to support CB_NOTIFY. > > Maybe we will add support for directory delegations and notifications at > some time in the future, but before that happens, somebody needs to > convince me that they are useful. Currently there is very little > documentation to support any assertion that they are... > > Cheers > Trond > > -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
