OK, what does it do more than FSAL_MEM?

You should be able to eliminate the dirent cache (by setting MDCACHE { Dir_Chunk = 0; }, but since you need some way to find an inode by handle, you might as well allow mdcache to do that for you, ideally mdcache will be large enough to hold all your entries.

Frank

From: Alok Sinha [mailto:alok@spillbox.io]
Sent: Tuesday, September 28, 2021 12:03 PM
To: Frank Filz <ffilzlnx@mindspring.com>
Cc: Ganesha-devel <devel@lists.nfs-ganesha.org>
Subject: [NFS-Ganesha-Devel] Re: disable inode & dirents cache

It is pure memory FSAL, no backend storage.

-alok

On Tue, Sep 28, 2021 at 11:36 AM Frank Filz <ffilzlnx@mindspring.com> wrote:

You might be able to get away without a dirent cache, but the mdcache is also the handle cache.

What do you mean by “FSAL is in the main memory”? Is it a pure memory FSAL or does it have some kind of back end?

Frank

From: Alok Sinha [mailto:alok@spillbox.io]
Sent: Tuesday, September 28, 2021 9:18 AM
To: Ganesha-devel <devel@lists.nfs-ganesha.org>
Subject: [NFS-Ganesha-Devel] disable inode & dirents cache

My FSAL is in the main memory.  Should I disable inode and dirents caching?

If so, what all I save in terms of memory and open FDs. I am not worried much about saving

open FDs but I do not want memory to get occupied without much benefit.

How do I disable inode and dirents?

Version: 2.8.3

-alok