From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: filesystem client mapping of uid_t/gid_t field in lookup
Date: Sat, 14 May 2005 12:38:57 +0100
Message-ID: <20050514113857.GA19653@mail.shareable.org>
References: <42852F4D.4020804@austin.rr.com> <1116052679.13863.38.camel@lade.trondhjem.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Steve French <smfrench@austin.rr.com>,
	linux-fsdevel@vger.kernel.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mail.shareable.org ([81.29.64.88]:13526 "EHLO
	mail.shareable.org") by vger.kernel.org with ESMTP id S262742AbVENLjK
	(ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Sat, 14 May 2005 07:39:10 -0400
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Content-Disposition: inline
In-Reply-To: <1116052679.13863.38.camel@lade.trondhjem.org>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

Trond Myklebust wrote:
> In NFSv4 (which is the only NFS implementation that supports native
> uid/gid mapping since it defines a globally unique username/groupname
> space for use on the wire) the uid/gid mapping is done using upcalls to
> a userland daemon on both the client and server side. A cache is used in
> order to avoid too many upcalls. Why would this sort of approach be
> impractical for CIFS?

It would be even nicer if they could share the same mapping daemon.

-- Jamie