From: Christoph Martin <martin@uni-mainz.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Andy Adamson <andros@netapp.com>,
Markus Tacke <tacke@uni-mainz.de>, <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] make nfsd_drc_max_mem configurable
Date: Thu, 20 Aug 2015 11:30:51 +0200 [thread overview]
Message-ID: <55D59E4B.9010404@uni-mainz.de> (raw)
In-Reply-To: <559A7BBF.2080201@uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
Hi Bruce
>
> I found the following calls to kmem_cache_create:
>
>>
>> nfs4state.c:2635: openowner_slab = kmem_cache_create("nfsd4_openowners",
>> nfs4state.c:2639: lockowner_slab = kmem_cache_create("nfsd4_lockowners",
>> nfs4state.c:2643: file_slab = kmem_cache_create("nfsd4_files",
>> nfs4state.c:2647: stateid_slab = kmem_cache_create("nfsd4_stateids",
>> nfs4state.c:2651: deleg_slab = kmem_cache_create("nfsd4_delegations",
>> nfscache.c:168: drc_slab = kmem_cache_create("nfsd_drc", sizeof(struct svc_cacherep),
>
> At a first look, they all use different methods to administer this
> memory if at all.
>
Another solution would be to simply remove the upper limit for the drc
cache size.
What do you think? How do we solve this problem?
Christoph
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-08-20 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 12:48 [PATCH] make nfsd_drc_max_mem configurable Christoph Martin
2015-06-18 16:16 ` J. Bruce Fields
2015-07-06 12:59 ` Christoph Martin
2015-08-20 9:30 ` Christoph Martin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55D59E4B.9010404@uni-mainz.de \
--to=martin@uni-mainz.de \
--cc=andros@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tacke@uni-mainz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox