From mboxrd@z Thu Jan 1 00:00:00 1970 From: Trond Myklebust Subject: Re: [RFC] Support for stackable file systems on top of nfs Date: Fri, 11 Nov 2005 14:42:19 -0500 Message-ID: <1131738139.8793.63.camel@lade.trondhjem.org> References: <17268.51608.767900.660180@gargle.gargle.HOWL> <17268.61825.107360.630709@gargle.gargle.HOWL> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: fsdevel , Shaya Potter , nfsv4 , Bryan Henderson , Dave Kleikamp Return-path: To: Nikita Danilov In-Reply-To: <17268.61825.107360.630709@gargle.gargle.HOWL> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfsv4-bounces@linux-nfs.org Errors-To: nfsv4-bounces@linux-nfs.org List-Id: linux-fsdevel.vger.kernel.org On Fri, 2005-11-11 at 22:31 +0300, Nikita Danilov wrote: > What one may argue, on the other hand, is that struct file should be > split into generic and file system specific part, with the low level > code only using the latter. This would be acceptable (and indeed we already do something like this in the low-level NFS read/write code), but would it really make much of a difference to stackable filesystems? Tracking the full struct file should be no more difficult than tracking the file->private_data. Cheers, Trond