From: Jeff Garzik Subject: Re: Attempt at "stat light" implementation Date: Tue, 07 Apr 2009 13:38:22 -0400 Message-ID: <49DB8F8E.9010605@garzik.org> References: <20090407062356.GA1336463@fiona.linuxhacker.ru> <20090407173248.GC31824@shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Oleg Drokin , linux-fsdevel@vger.kernel.org, LKML To: Jamie Lokier Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:52166 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752729AbZDGRi2 (ORCPT ); Tue, 7 Apr 2009 13:38:28 -0400 In-Reply-To: <20090407173248.GC31824@shareable.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Jamie Lokier wrote: > Once you have fine-grained selection of stat fields - it's natural to > ask why not allow _additional_ stat fields in an future-extensible > fashion? A few things would be handy sometimes, such as inode > generation number, modification generation number (to detect changes > across reboots), and extra flags indicating COW or other properties. That's quite an interesting thought... until you run out of flags, the stat structure becomes a bit more flexible. Jeff