Open fd tracking is an area Ganesha actually needs some additional work,
however, the tracking in the non-support_ex methods did not limit the number of
NFS v4 opens in any way, it just was used to manage how many fds Ganesha kept
open for I/O access to files.
With support_ex, an fd is associated with each file clients have open (NFS v4),
and additional fds are (may) be used per file/lock owner pair.
Ultimately we do need to have a limit on how much state (NFS v4 open,
NLM_SHARE, locks, delegations, layouts) is active.
Frank
From: Naresh Babu [mailto:snareshb...@gmail.com]
Sent: Saturday, February 11, 2017 4:21 PM
To: nfs-ganesha-devel@lists.sourceforge.net
Subject: [Nfs-ganesha-devel] how does ganesha limit number of FDs
If a particular FSAL implements extended ops like open2/write2/read2/commit2,
open_fd_count doesn't get tracked. Then, how does ganesha limit the number of
open FDs? In general, what is the rationale behind not tracking open fd count?
Thanks,
Naresh
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------------------------------------------------------
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
