From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Patrick J. LoPresti" Subject: Re: Proposal: Use hi-res clock for file timestamps Date: Fri, 13 Aug 2010 13:53:57 -0700 Message-ID: References: <1281726579.2810.10.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel To: john stultz Return-path: In-Reply-To: <1281726579.2810.10.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On Fri, Aug 13, 2010 at 12:09 PM, john stultz wrote: > > So other then "show some numbers", my only thought that might make the > patch more attractive is that rather than a global change, or a static > CONFIG_ option, would it maybe make more sense as a mount option? I really like this idea. Consider the following "revision 2" of my proposal: 1) Add a function pointer "current_fs_time" to struct super_block. 2) Replace all calls of the form: current_fs_time(sb); with sb->current_fs_time(sb); 3) Arrange for the default value to point to the current implementation. These first three could be one patch. They change no functionality; they just enable the next step. Finally: 4) Add a mount option to cause sb->current_fs_time(sb) to use the hi-res implementation. Comments? - Pat -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html