public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Simon Kirby <sim@hostway.ca>
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, 03 Sep 2009 16:49:25 -0400	[thread overview]
Message-ID: <1252010965.18338.63.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20090903200550.GB5257@hostway.ca>

On Thu, 2009-09-03 at 13:05 -0700, Simon Kirby wrote:
> 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.

That's a separate issue.

I'm working on increasing the idmapper scalability, however another
project is currently taking up most of my time. I can't guarantee that
the revised idmapper code will be finished in time to allow for
inclusion in 2.6.32.

> Why on earth does NFSv4 force the use of names?

NFSv4 aspires to be an internet-wide protocol, and so you cannot use
uids/gids: they just aren't guaranteed to represent a unique user
outside your local LDAP/NIS or /etc/passwd domain. Furthermore, uids and
gids are a posix construct. They simply don't work in environments where
you may have lots of non-posix systems.

Trond


  reply	other threads:[~2009-09-03 20:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A92A25A.4050608@yohan.staff.proxad.net>
     [not found] ` <20090824162155.ce323f08.akpm@linux-foundation.org>
     [not found]   ` <4A96463E.5080002@corp.free.fr>
     [not found]     ` <4A9C34F8.2010307@corp.free.fr>
     [not found]       ` <4A9C34F8.2010307-CZvJ5kAzflf985uAA1p3mw@public.gmane.org>
2009-09-03  0:06         ` VM issue causing high CPU loads 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                 ` VM issue causing high CPU loads Simon Kirby
2009-09-03 20:49                   ` Trond Myklebust [this message]
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=1252010965.18338.63.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --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=sim@hostway.ca \
    --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