nfs: Introduce tunable for memory consumption

NFS has used a common define called the mem-factor to determine
how much memory is allocated for the following items:

o inode table
o local structures used by nfs for storing fop state
o local structures used by nfs3 for storing nfs op state

These are all allocated through the mem-pool. The factor is multiplied by
a multiple that is specific to each data structure. For eg.

define GF_NFS_CONCURRENT_OPS_MULT     15
define GF_NFS_INODE_LRU_MULT          6000

The first value is used for allocating a mem-pool for storing
state for each fop or nfs op that is currently being handled. Knowing that linux
allows at most 128 in-flight requests, this multiple combined with the default
mem-factor of 15 gives us 225 slots in the mem-pool for the local structures.

Similarly, 6000*15 gives us a space of 90k inodes in the lru.

That means, increasing the common mem-factor will allow increasing the perf
under some conditions. This patch introduces the mem-factor as a configurable
option.

Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

BUG: 2277 (Regression in Gluster NFS re-read performance)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2277

0 files changed, 0 insertions, 0 deletions