public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 15:22:53 -0700	[thread overview]
Message-ID: <20090903222253.GA8405@hostway.ca> (raw)
In-Reply-To: <1252010965.18338.63.camel@heimdal.trondhjem.org>

On Thu, Sep 03, 2009 at 04:49:25PM -0400, Trond Myklebust wrote:

> 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.

Sure, improving it would be nice for cases where it's needed, but in
environments where all IDs are consistent (by design), it just seems
silly to force this extra work for zero gain.

> 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.

So, for environments with all POSIX systems, what do you think about
perhaps a mount or export flag that violates the spec on purpose to allow
numeric IDs to be used?

I can understand that the quiet use of IDs if name-to-user mapping fails
will cause security issues in environments without consistent users, so
it would now be unsafe to turn this on silently.  However, making this
an option seems reasonable to me.

(Not that I know what I'm doing.)

Simon-

  reply	other threads:[~2009-09-03 22:22 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               ` VM issue causing high CPU loads Simon Kirby
2009-09-03 20:49                 ` Trond Myklebust
2009-09-03 22:22                   ` Simon Kirby [this message]
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=20090903222253.GA8405@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