From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. R. Okajima" Subject: Re: [PATCH v2] d_ino considered harmful Date: Fri, 18 Jun 2010 11:57:52 +0900 Message-ID: <7385.1276829872@jrobl> References: <20100616185913.GA15566@shell> <20100616195359.GA24382@shell> <1276721084.13788.53.camel@lap75545.ornl.gov> <30568.1276797848@jrobl> Cc: David Dillow , Valerie Aurora , Alexander Viro , Christoph Hellwig , Miklos Szeredi , Jan Blunck , Jamie Lokier , David Woodhouse , Arnd Bergmann , Andreas Dilger , "linux-kernel@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" To: Andreas Dilger Return-path: Received: from mtoichi12.ns.itscom.net ([219.110.2.182]:37436 "EHLO mtoichi12.ns.itscom.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755537Ab0FRC7t (ORCPT ); Thu, 17 Jun 2010 22:59:49 -0400 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Andreas Dilger: > As the name implies, it is very extN specific. For Lustre 2.0 we use a > different method to get O(1) FID (inode number) to pathname(s) > lookup. Each file stores an xattr with the {parent FID, filename} > tuples for each link to the file, whenever an inode is created, > linked, unlinked, or renamed. Honestly speaking, this approach is the one which came to my mind when I read David's mail. Andreas's approach and explanation is perfect as I should admire. Thank you J. R. Okajima