From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BB07AE7E62F for ; Tue, 26 Sep 2023 12:11:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234541AbjIZMLI (ORCPT ); Tue, 26 Sep 2023 08:11:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52270 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234540AbjIZMLH (ORCPT ); Tue, 26 Sep 2023 08:11:07 -0400 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 95F0610E; Tue, 26 Sep 2023 05:11:00 -0700 (PDT) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D25C1C433C7; Tue, 26 Sep 2023 12:10:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1695730260; bh=O2z7OioDXm74KMl0zRdCUt79HUvbW522ehMNV8lx44s=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=M73Byivq+oBHbE1CDYzwaclHKGN2Ea0ZQd9tRJ6IGot1wG2PE8CwkZ+DuJ65sbqyH DsTvyI3TGqTWYqZxpp1NCd6jzikRLUnbrNgtKgWEFTcvdy+GHPeYvxtOSi5OXLFGEz 7RO8n7IiDbc8D+jEAFi7ug8f5rPLIX3IEh47czWRqaZHctRx0VdZ42AYMB4sn4v4Hx LKyuFGTjGCIwjFnDM+2VE+jSW0OPAPbyDTAF5p9Qeba9Wr+6EzIdaLEyr1wQV4JMi+ 105RQyKapSzvRVeQ6+ycfyY5wx7OhzsvksWOK/3NR1ZWa4bFOmr8ydOAAqiMV7PVXf XjKtdx7YAwoYw== Date: Tue, 26 Sep 2023 14:10:54 +0200 From: Christian Brauner To: Jeff Layton Cc: NeilBrown , Alexander Viro , Chuck Lever , Olga Kornievskaia , Dai Ngo , Tom Talpey , Chandan Babu R , "Darrick J. Wong" , Dave Chinner , Jan Kara , Linus Torvalds , Kent Overstreet , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org, linux-xfs@vger.kernel.org Subject: Re: [PATCH v8 0/5] fs: multigrain timestamps for XFS's change_cookie Message-ID: <20230926-anregen-einplanen-6fd7d1a89ef8@brauner> References: <20230922-ctime-v8-0-45f0c236ede1@kernel.org> <20230924-mitfeiern-vorladung-13092c2af585@brauner> <169559548777.19404.13247796879745924682@noble.neil.brown.name> <9b81a1f52b4dc777dbb5259b2e12e90eba0ff507.camel@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <9b81a1f52b4dc777dbb5259b2e12e90eba0ff507.camel@kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org > > Some NFS servers run in userspace, and they would a "clear user" of this > > functionality. > > > > Indeed. Also, all of the programs that we're concerned about breaking > here (make, rsync, etc.) could benefit from proper fine-grained > timestamps: > > Today, when they see two identical timestamps on files, these programs > have to assume the worst: rsync has to do the copy, make has to update > the target, etc. With a real distinguishable fine-grained timestamps, > these programs would likely be more efficient and some of these unneeded > operations would be avoided. The whole sales pitch falls flat if we end up with wrong ordering of timestamps which caused us to revert this. So unless this is fixed we shouldn't expose this to userspace again.