From: Randy Dunlap <rdunlap@infradead.org>
To: Jeff Layton <jlayton@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Chandan Babu R <chandan.babu@oracle.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: Dave Chinner <david@fromorbit.com>,
Andi Kleen <ak@linux.intel.com>,
Christoph Hellwig <hch@infradead.org>,
Uros Bizjak <ubizjak@gmail.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
kernel-team@fb.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-mm@kvack.org,
linux-nfs@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 5/9] Documentation: add a new file documenting multigrain timestamps
Date: Tue, 9 Jul 2024 16:50:24 -0700 [thread overview]
Message-ID: <420ac42f-dad2-4fd9-b36a-6405d14b6e25@infradead.org> (raw)
In-Reply-To: <20240708-mgtime-v4-5-a0f3c6fb57f3@kernel.org>
On 7/8/24 8:53 AM, Jeff Layton wrote:
> Add a high-level document that describes how multigrain timestamps work,
> rationale for them, and some info about implementation and tradeoffs.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
> Documentation/filesystems/multigrain-ts.rst | 120 ++++++++++++++++++++++++++++
> 1 file changed, 120 insertions(+)
>
> diff --git a/Documentation/filesystems/multigrain-ts.rst b/Documentation/filesystems/multigrain-ts.rst
> new file mode 100644
> index 000000000000..e4f52a9e3c51
> --- /dev/null
> +++ b/Documentation/filesystems/multigrain-ts.rst
> @@ -0,0 +1,120 @@
> +Inode Timestamp Ordering
> +========================
> +
> +In addition just providing info about changes to individual files, file
In addition to just
> +timestamps also serve an important purpose in applications like "make". These
> +programs measure timestamps in order to determine whether source files might be
> +newer than cached objects.
next prev parent reply other threads:[~2024-07-09 23:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 15:53 [PATCH v4 0/9] fs: multigrain timestamp redux Jeff Layton
2024-07-08 15:53 ` [PATCH v4 1/9] fs: add infrastructure for multigrain timestamps Jeff Layton
2024-07-08 18:39 ` Darrick J. Wong
2024-07-08 18:47 ` Jeff Layton
2024-07-08 15:53 ` [PATCH v4 2/9] fs: tracepoints around multigrain timestamp events Jeff Layton
2024-07-08 15:53 ` [PATCH v4 3/9] fs: add percpu counters for significant " Jeff Layton
2024-07-08 15:53 ` [PATCH v4 4/9] fs: have setattr_copy handle multigrain timestamps appropriately Jeff Layton
2024-07-08 15:53 ` [PATCH v4 5/9] Documentation: add a new file documenting multigrain timestamps Jeff Layton
2024-07-09 23:50 ` Randy Dunlap [this message]
2024-07-08 15:53 ` [PATCH v4 6/9] xfs: switch to " Jeff Layton
2024-07-08 18:47 ` Darrick J. Wong
2024-07-08 18:51 ` Jeff Layton
2024-07-08 19:00 ` Jeff Layton
2024-07-08 19:01 ` Darrick J. Wong
2024-07-08 15:53 ` [PATCH v4 7/9] ext4: " Jeff Layton
2024-07-08 15:53 ` [PATCH v4 8/9] btrfs: convert " Jeff Layton
2024-07-08 15:53 ` [PATCH v4 9/9] tmpfs: add support for " Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=420ac42f-dad2-4fd9-b36a-6405d14b6e25@infradead.org \
--to=rdunlap@infradead.org \
--cc=adilger.kernel@dilger.ca \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=clm@fb.com \
--cc=corbet@lwn.net \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kent.overstreet@linux.dev \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tytso@mit.edu \
--cc=ubizjak@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).