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

2017-02-22 Thread Frank Filz
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 to

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

2017-02-22 Thread GerritHub
>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 of unused cookie field in

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

2017-02-22 Thread GerritHub
>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 FSAL_PSEUDO to return the

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Add glist_next_entry function to get the next item in a glist

2017-02-22 Thread GerritHub
>From Frank Filz : Frank Filz has uploaded a new change for review. ( https://review.gerrithub.io/350077 Change subject: Add glist_next_entry function to get the next item in a glist .. Add glist_next_entry function to get the

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Add dirent chunking configuration

2017-02-22 Thread GerritHub
>From Frank Filz : Frank Filz has uploaded a new change for review. ( https://review.gerrithub.io/350078 Change subject: Add dirent chunking configuration .. Add dirent chunking configuration Change-Id: I6868dc899db6732488e67

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

2017-02-22 Thread GerritHub
>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: Id206255b2bffd558438981e267f1849bfae69597 Signed

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

2017-02-22 Thread GerritHub
>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 readdir. This still needs dire

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: SAL - Keep a pointer to the obj owning the state

2017-02-22 Thread GerritHub
>From Daniel Gryniewicz : Daniel Gryniewicz has uploaded a new change for review. ( https://review.gerrithub.io/350056 Change subject: SAL - Keep a pointer to the obj owning the state .. SAL - Keep a pointer to the obj owning

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

2017-02-22 Thread Frank Filz
> 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] Change in ffilz/nfs-ganesha[next]: release file sys after file sys is unclaimed

2017-02-22 Thread GerritHub
>From : madhu.punj...@in.ibm.com has uploaded a new change for review. ( https://review.gerrithub.io/349969 Change subject: release file sys after file sys is unclaimed .. release file sys after file sys is unclaimed Currentl

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

2017-02-22 Thread Daniel Gryniewicz
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. > > > Consider

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

2017-02-22 Thread patrice.lucas
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 "trunca