From: Simon Kirby <sim@hostway.ca>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Yohan <ytordjman@corp.free.fr>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Neil Brown <neilb@suse.de>,
"J. Bruce Fields" <bfields@fieldses.org>,
mikevs@xs4all.net
Subject: Re: VM issue causing high CPU loads
Date: Thu, 3 Sep 2009 13:05:50 -0700 [thread overview]
Message-ID: <20090903200550.GB5257@hostway.ca> (raw)
In-Reply-To: <1251986526.18338.29.camel@heimdal.trondhjem.org>
On Thu, Sep 03, 2009 at 10:02:06AM -0400, Trond Myklebust wrote:
> OK, so 16 hash buckets are likely to be filled with ~10^6 entries each.
> I can see that might be a performance issue...
We have a similar setup with millions of UIDs over NFS (currently NFSv3).
I _wish_ there were a way to use NFSv4 without having to use name-mapped
UIDs and GIDs, since our user and group names come from MySQL anyway, and
are guaranteed to be consistent across machines.
Why on earth does NFSv4 force the use of names?
I was considering hacking the code to stick IDs in there anyway, but I
haven't looked at the feasibility of this. I suspect this would break or
complicate other things, but the current NFSv4 design just seems like an
incredible waste for this case.
Simon-
next prev parent reply other threads:[~2009-09-03 20:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 14:23 VM issue causing high CPU loads Yohan
2009-08-24 23:21 ` Andrew Morton
2009-08-26 11:08 ` Mel Gorman
2009-08-26 11:55 ` Yohan
2009-08-26 11:53 ` Yohan
2009-08-27 8:39 ` Yohan
2009-08-31 20:39 ` Yohan
2009-09-03 0:06 ` Andrew Morton
2009-09-03 13:01 ` Trond Myklebust
2009-09-03 13:39 ` Yohan
2009-09-03 14:02 ` Trond Myklebust
2009-09-03 14:08 ` Yohan
2009-09-03 14:35 ` sunrpc: dynamically allocate credcache hashtables [was: Re: VM issue causing high CPU loads] Miquel van Smoorenburg
2009-09-03 20:05 ` Simon Kirby [this message]
2009-09-03 20:49 ` VM issue causing high CPU loads Trond Myklebust
2009-09-03 22:22 ` Simon Kirby
2009-09-04 12:31 ` Trond Myklebust
2009-09-03 21:21 ` Muntz, Daniel
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=20090903200550.GB5257@hostway.ca \
--to=sim@hostway.ca \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mikevs@xs4all.net \
--cc=neilb@suse.de \
--cc=trond.myklebust@fys.uio.no \
--cc=ytordjman@corp.free.fr \
/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