Wondering about NLM_HOST_MAX ... doesn't anyone understand this code?
Subsystems (2)
Hi,
I've been looking at NLM_HOST_MAX in fs/lockd/host.c, as we have a patch in SLES that makes it configurable, and the patch needs to either go upstream or out the window...
But the code that uses NLM_HOST_MAX is weird! Look:
#define NLM_HOST_EXPIRE ((nrhosts > NLM_HOST_MAX)? 300 * HZ : 120 * HZ)
#define NLM_HOST_COLLECT ((nrhosts > NLM_HOST_MAX)? 120 * HZ : 60 * HZ)
So if the number of hosts is more than the maximum (64), we *increase* the expiry time and the garbage collection interval.
You would think they should be decreased when we have exceeded the max, so we can get rid of more old entries more quickly. But no, they are increased.
And in the code where we add a host to the list of hosts:
if (++nrhosts > NLM_HOST_MAX) next_gc = 0;
So when we go over the limit, we garbage collect straight away, but almost certainly do nothing because we've just given every host an extra 3 minutes that it is allowed to live.
We could change the '>' to '<' which would make the code make sense at least, but I don't think we want to. A server could easily have more than 64 clients doing lock requests, and we don't want to make life harder for clients just because there are more of them.
I think we should just get rid of NLM_HOST_MAX altogether. Old hosts will still go away in a few minutes and pushing them out quickly shouldn't be needed.
So: any comments on the above or on the patch below. I've chosen to go with "discard hosts older than 5 minutes every 2 minutes" rather than "discard hosts older than 2 minutes every minute" even though the latter is what would have been in effect most of the time, as it seems more like what was intended.
Thanks,
NeilBrown
### Diffstat output
./fs/lockd/host.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)
fs/lockd/host.c +2 -6
@@ -19,12 +19,11 @@#define NLMDBG_FACILITY NLMDBG_HOSTCACHE -#define NLM_HOST_MAX 64#define NLM_HOST_NRHASH 32#define NLM_ADDRHASH (addr) (ntohl(addr) & (NLM_HOST_NRHASH-1))#define NLM_HOST_REBIND (60 * HZ) -#define NLM_HOST_EXPIRE ((nrhosts > NLM_HOST_MAX)? 300 * HZ : 120 * HZ) -#define NLM_HOST_COLLECT ((nrhosts > NLM_HOST_MAX)? 120 * HZ : 60 * HZ) +#define NLM_HOST_EXPIRE (300 * HZ) +#define NLM_HOST_COLLECT (120 * HZ)static struct hlist_head nlm_hosts[NLM_HOST_NRHASH ];static unsigned long next_gc;
@@ -142,9 +141,6 @@ nlm_lookup_host(int server, const structINIT_LIST_HEAD (&host->h_granted);INIT_LIST_HEAD (&host->h_reclaim); -if (++nrhosts >NLM_HOST_MAX ) - next_gc =0 ; - out:mutex_unlock (&nlm_host_mutex);return host;
A message that is not in the archive (sent off-list or not yet received): 18346.31720.497379.823879-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org
Quoted 42 lines · On Thu, 7 Feb 2008 14:32:56 +1100 Neil Brown <[email protected]> wrote:
Hi,
I've been looking atNLM_HOST_MAXinfs/lockd/host.c, as we have a patch in SLES that makes it configurable, and the patch needs to either go upstream or out the window...But the code that uses
NLM_HOST_MAXis weird! Look:#define
NLM_HOST_EXPIRE((nrhosts >NLM_HOST_MAX)? 300 * HZ : 120 * HZ)
#defineNLM_HOST_COLLECT((nrhosts >NLM_HOST_MAX)? 120 * HZ : 60 * HZ)So if the number of hosts is more than the maximum (64), we *increase* the expiry time and the garbage collection interval.
You would think they should be decreased when we have exceeded the max, so we can get rid of more old entries more quickly. But no, they are increased.And in the code where we add a host to the list of hosts:
if (++nrhosts > NLM_HOST_MAX) next_gc = 0;So when we go over the limit, we garbage collect straight away, but almost certainly do nothing because we've just given every host an extra 3 minutes that it is allowed to live.
We could change the '>' to '<' which would make the code make sense at least, but I don't think we want to. A server could easily have more than 64 clients doing lock requests, and we don't want to make life harder for clients just because there are more of them.
I think we should just get rid of
NLM_HOST_MAXaltogether. Old hosts will still go away in a few minutes and pushing them out quickly shouldn't be needed.So: any comments on the above or on the patch below. I've chosen to go with "discard hosts older than 5 minutes every 2 minutes" rather than "discard hosts older than 2 minutes every minute" even though the latter is what would have been in effect most of the time, as it seems more like what was intended.
Quoted 6 lines
Thanks,
NeilBrownSigned-off-by Neil Brown <[email protected]>
As far as I can tell, the only "problem" with having a lot of nlm_host entries is that they take up a little memory and maybe a little extra CPU time when we walk over them in the lists. NLM_HOST_MAX doesn't really seem to be needed anymore on any sort of modern hardware.
ACK
Quoted 37 lines
### Diffstat output
./fs/lockd/host.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)diff
.prev/fs/lockd/host.c./fs/lockd/host.cfs/lockd/host.c +2
-7@@ -19,12 +19,11 @@#define NLMDBG_FACILITY NLMDBG_HOSTCACHE -#define NLM_HOST_MAX 64#define NLM_HOST_NRHASH 32#define NLM_ADDRHASH (addr) (ntohl(addr) & (NLM_HOST_NRHASH-1))#define NLM_HOST_REBIND (60 * HZ) -#define NLM_HOST_EXPIRE ((nrhosts > NLM_HOST_MAX)? 300 * HZ : 120 * HZ) -#define NLM_HOST_COLLECT ((nrhosts > NLM_HOST_MAX)? 120 * HZ : 60 * HZ) +#define NLM_HOST_EXPIRE (300 * HZ) +#define NLM_HOST_COLLECT (120 * HZ)static struct hlist_head nlm_hosts[NLM_HOST_NRHASH ];static unsigned long next_gc;@@ -142,9 +141,6 @@ nlm_lookup_host(int server, const structINIT_LIST_HEAD (&host->h_granted);INIT_LIST_HEAD (&host->h_reclaim); -if (++nrhosts >NLM_HOST_MAX ) - next_gc =0 ; - out:mutex_unlock (&nlm_host_mutex);return host; -To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 1 line
Jeff Layton <[email protected]>
Hi Neil-
I don't have a problem with removing the variant expiry behavior -- in fact, I think it might be better if NLM host garbage collection was done only under memory pressure.
But see below.
Quoted 72 lines · Neil Brown
Hi,
I've been looking atNLM_HOST_MAXinfs/lockd/host.c, as we have a patch in SLES that makes it configurable, and the patch needs to either go upstream or out the window...But the code that uses
NLM_HOST_MAXis weird! Look:#define
NLM_HOST_EXPIRE((nrhosts >NLM_HOST_MAX)? 300 * HZ : 120 * HZ)
#defineNLM_HOST_COLLECT((nrhosts >NLM_HOST_MAX)? 120 * HZ : 60 * HZ)So if the number of hosts is more than the maximum (64), we *increase* the expiry time and the garbage collection interval.
You would think they should be decreased when we have exceeded the max, so we can get rid of more old entries more quickly. But no, they are increased.And in the code where we add a host to the list of hosts:
if (++nrhosts > NLM_HOST_MAX) next_gc = 0;So when we go over the limit, we garbage collect straight away, but almost certainly do nothing because we've just given every host an extra 3 minutes that it is allowed to live.
We could change the '>' to '<' which would make the code make sense at least, but I don't think we want to. A server could easily have more than 64 clients doing lock requests, and we don't want to make life harder for clients just because there are more of them.
I think we should just get rid of
NLM_HOST_MAXaltogether. Old hosts will still go away in a few minutes and pushing them out quickly shouldn't be needed.So: any comments on the above or on the patch below. I've chosen to go with "discard hosts older than 5 minutes every 2 minutes" rather than "discard hosts older than 2 minutes every minute" even though the latter is what would have been in effect most of the time, as it seems more like what was intended.
Thanks,
NeilBrownSigned-off-by Neil Brown <[email protected]>### Diffstat output
./fs/lockd/host.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)diff
.prev/fs/lockd/host.c./fs/lockd/host.cfs/lockd/host.c +2
-3@@ -19,12 +19,11 @@#define NLMDBG_FACILITY NLMDBG_HOSTCACHE -#define NLM_HOST_MAX 64#define NLM_HOST_NRHASH 32#define NLM_ADDRHASH (addr) (ntohl(addr) & (NLM_HOST_NRHASH-1))#define NLM_HOST_REBIND (60 * HZ) -#define NLM_HOST_EXPIRE ((nrhosts > NLM_HOST_MAX)? 300 * HZ : 120 * HZ) -#define NLM_HOST_COLLECT ((nrhosts > NLM_HOST_MAX)? 120 * HZ : 60 * HZ) +#define NLM_HOST_EXPIRE (300 * HZ) +#define NLM_HOST_COLLECT (120 * HZ)static struct
hlist_headnlm_hosts[NLM_HOST_NRHASH];
static unsigned longnext_gc;
fs/lockd/host.c nlm_lookup_host(int server, const struct · line 147
Quoted 6 lines
fs/lockd/host.c +0
-3@@ -142,9 +141,6 @@ nlm_lookup_host(int server, const structINIT_LIST_HEAD (&host->h_granted);INIT_LIST_HEAD (&host->h_reclaim); -if (++nrhosts >NLM_HOST_MAX ) - next_gc =0 ; -
AFAICT this is the only place where nrhosts is bumped. So you should either get rid of nrhosts all together, or leave in a ++nrhosts; somewhere.
fs/lockd/host.c nlm_lookup_host(int server, const struct · line 146
Quoted 3 lines
fs/lockd/host.c +0
-0out:mutex_unlock (&nlm_host_mutex);return host;
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
Quoted 5 lines · On Thursday February 7, [email protected] wrote:
Hi Neil-
I don't have a problem with removing the variant expiry behavior -- in fact, I think it might be better if NLM host garbage collection was done only under memory pressure.
Cool, thanks.
Quoted 9 lines
fs/lockd/host.c nlm_lookup_host(int server, const struct · line 147
Quoted 4 lines
fs/lockd/host.c +0
-3-if (++nrhosts >NLM_HOST_MAX ) - next_gc =0 ; -AFAICT this is the only place where nrhosts is bumped. So you should either get rid of nrhosts all together, or leave in a ++nrhosts; somewhere.
It is still used for a sanity check, and would be needed (I think) if we introduced a memory-pressure handler, so I'll leave it there and restore the "++nrhosts" - thanks for catching that.
Thanks,
NeilBrown