From: David Howells <dhowells@redhat.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: dhowells@redhat.com, Brian De Wolf <bldewolf@csupomona.edu>,
Linux NFS list <linux-nfs@vger.kernel.org>
Subject: Re: Issues using new idmapper in large sites
Date: Wed, 19 Jun 2013 15:07:10 +0100 [thread overview]
Message-ID: <7562.1371650830@warthog.procyon.org.uk> (raw)
In-Reply-To: <1371649292.5522.1.camel@leira.trondhjem.org>
Myklebust, Trond <Trond.Myklebust@netapp.com> wrote:
> > It's fast but...it also missed most of my users (it only has 503
> > cached, there are 36287 total). The refcount and number of keys
> > skyrocket even further on repeated runs but the number of missing
> > users remains the same.
Okay... I need to improve keyring capacity.
Current max keyring capacity is
(PAGE_SIZE - header) / sizeof(key *)
in other words, 500-ish on a 64-bit machine.
Let me have a play - in theory, it shouldn't be too hard; the main trick is
retaining RCU-based reading and, ideally, tree size. Plus if I can sort it
too...
David
prev parent reply other threads:[~2013-06-19 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 3:12 Issues using new idmapper in large sites Brian De Wolf
2013-06-19 13:41 ` Myklebust, Trond
2013-06-19 14:07 ` David Howells [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=7562.1371650830@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bldewolf@csupomona.edu \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).