On 8/7/17 9:42 AM, Frank Filz wrote:
It never has been. In cache_inode, a pin-ref kept it from being reaped, now
any ref beyond 1 keeps it.
Guess we need to do something about that... We need to put limits on state
somewhere, that would take care of it mostly. We could still have some files in
excess of high water mark due to active I/O threads, but that quantity is
limited by the worker thread count.
That won't be true as the async I-O is added. Fewer threads will
handle many more connections.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
