From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH 5/6] xfs: move non-inline symlinks to the pagecache Date: Sat, 25 Apr 2015 15:57:28 +0100 Message-ID: <20150425145728.GE889@ZenIV.linux.org.uk> References: <1429816064-10033-1-git-send-email-hch@lst.de> <1429816064-10033-6-git-send-email-hch@lst.de> <20150423222942.GK15810@dastard> <20150425141612.GA4153@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dave Chinner , xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org To: Christoph Hellwig Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:59698 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932899AbbDYO5c (ORCPT ); Sat, 25 Apr 2015 10:57:32 -0400 Content-Disposition: inline In-Reply-To: <20150425141612.GA4153@lst.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sat, Apr 25, 2015 at 04:16:12PM +0200, Christoph Hellwig wrote: > Al, what do you think about adding a new > > i_link member to the union of i_pipe, i_bdev and i_cdev. That we > we can cache a link acquired by any way for direct use in the VFS. > > This has a few use cases: inline links can be set up directly > when reading the inode, and we never need to call into ->follow_link. > > Formats like the XFS v5 symlinks can be read in once by whatever > way we want, and following accesses can be done RCU safe and > without calling into the filesystem. > > Note that caching the symlink in a kmalloc'ed buffer might be > more efficient than the pagecache for most cases anyway. Hmm... When would you free the sucker?