[Nfs-ganesha-devel] Work in Progress Readdir Chunking Posted

I have a first pass that works and passes pynfs! It isn't quite correct in that a rename into a directory or a create doesn't invalidate the dirent cache and thus a readdir might not show the new file. Unlink and rename out of a directory need not invalidate and should work properly. Also left

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Get rid of unused cookie field in struct mdcache_populate_cb...

>From Frank Filz : Frank Filz has uploaded a new change for review. ( https://review.gerrithub.io/350076 Change subject: Get rid of unused cookie field in struct mdcache_populate_cb_state .. Get rid

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Fix FSAL_PSEUDO to return the cookie for the NEXT entry for ...

>From Frank Filz : Frank Filz has uploaded a new change for review. ( https://review.gerrithub.io/350080 Change subject: Fix FSAL_PSEUDO to return the cookie for the NEXT entry for each dirent .. Fix

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Add glist_last_entry

>From Frank Filz : Frank Filz has uploaded a new change for review. ( https://review.gerrithub.io/350079 Change subject: Add glist_last_entry .. Add glist_last_entry Change-Id:

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: WIP Add directory chunking for readdir.

>From Frank Filz : Frank Filz has uploaded a new change for review. ( https://review.gerrithub.io/350081 Change subject: WIP Add directory chunking for readdir. .. WIP Add directory chunking for

Re: [Nfs-ganesha-devel] FSAL_PROXY with NVSv4 protocol : no way to truncate ?

> On 02/22/2017 04:53 AM, patrice.lu...@cea.fr wrote: > > Hi Frank, > > > > > > As I said yesterday during our last concall, I realized that the > > current FSAL_PROXY use the v4 protocol and not the v4.1. My previous > > submitted patchs to implement support_ex assumed FSAL_PROXY was > using

Re: [Nfs-ganesha-devel] FSAL_PROXY with NVSv4 protocol : no way to truncate ?

On 02/22/2017 04:53 AM, patrice.lu...@cea.fr wrote: > Hi Frank, > > > As I said yesterday during our last concall, I realized that the current > FSAL_PROXY use the v4 protocol and not the v4.1. My previous submitted > patchs to implement support_ex assumed FSAL_PROXY was using v4.1. > > >

[Nfs-ganesha-devel] FSAL_PROXY with NVSv4 protocol : no way to truncate ?

Hi Frank, As I said yesterday during our last concall, I realized that the current FSAL_PROXY use the v4 protocol and not the v4.1. My previous submitted patchs to implement support_ex assumed FSAL_PROXY was using v4.1. Considering differences in v4 and v4.1, I don't see how doing a