From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>,
Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
Ext4 Developers List
<linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux btrfs Developers List
<linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
XFS Developers <xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux-Fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux API <linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Documenting MS_LAZYTIME
Date: Thu, 26 Feb 2015 09:49:39 +0100 [thread overview]
Message-ID: <54EEDE23.6080009@gmail.com> (raw)
In-Reply-To: <20150221025636.GB7922-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
Ted,
On 02/21/2015 03:56 AM, Theodore Ts'o wrote:
> On Fri, Feb 20, 2015 at 09:49:34AM -0600, Eric Sandeen wrote:
>>
>>> This mount option significantly reduces writes to the
>>> inode table for workloads that perform frequent random
>>> writes to preallocated files.
>>
>> This seems like an overly specific description of a single workload out
>> of many which may benefit, but what do others think? "inode table" is also
>> fairly extN-specific.
>
> How about somethign like "This mount significantly reduces writes
> needed to update the inode's timestamps, especially mtime and actime.
What is "actime" in the preceding line? Should it be "ctime"?
> Examples of workloads where this could be a large win include frequent
> random writes to preallocated files, as well as cases where the
> MS_STRICTATIME mount option is enabled."?
I think some version of the following text could also usefully go
into the page, but...
> (The advantage of MS_STRICTATIME | MS_LAZYTIME is that stat system
> calls will return the correctly updated atime, but those atime updates
> won't get flushed to disk unless the inode needs to be updated for
> file system / data consistency reasons, or when the inode is pushed
> out of memory, or when the file system is unmounted.)
I find the wording of there a little confusing. Is the following
a correct rewrite:
The advantage of MS_STRICTATIME | MS_LAZYTIME is that stat(2)
will return the correctly updated atime, but the atime updates
will be flushed to disk only when (1) the inode needs to be
updated for filesystem / data consistency reasons or (2) the
inode is pushed out of memory, or (3) the filesystem is
unmounted.)
?
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>, Eric Sandeen <sandeen@redhat.com>
Cc: mtk.manpages@gmail.com,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Linux btrfs Developers List <linux-btrfs@vger.kernel.org>,
XFS Developers <xfs@oss.sgi.com>,
linux-man@vger.kernel.org,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: Documenting MS_LAZYTIME
Date: Thu, 26 Feb 2015 09:49:39 +0100 [thread overview]
Message-ID: <54EEDE23.6080009@gmail.com> (raw)
In-Reply-To: <20150221025636.GB7922@thunk.org>
Ted,
On 02/21/2015 03:56 AM, Theodore Ts'o wrote:
> On Fri, Feb 20, 2015 at 09:49:34AM -0600, Eric Sandeen wrote:
>>
>>> This mount option significantly reduces writes to the
>>> inode table for workloads that perform frequent random
>>> writes to preallocated files.
>>
>> This seems like an overly specific description of a single workload out
>> of many which may benefit, but what do others think? "inode table" is also
>> fairly extN-specific.
>
> How about somethign like "This mount significantly reduces writes
> needed to update the inode's timestamps, especially mtime and actime.
What is "actime" in the preceding line? Should it be "ctime"?
> Examples of workloads where this could be a large win include frequent
> random writes to preallocated files, as well as cases where the
> MS_STRICTATIME mount option is enabled."?
I think some version of the following text could also usefully go
into the page, but...
> (The advantage of MS_STRICTATIME | MS_LAZYTIME is that stat system
> calls will return the correctly updated atime, but those atime updates
> won't get flushed to disk unless the inode needs to be updated for
> file system / data consistency reasons, or when the inode is pushed
> out of memory, or when the file system is unmounted.)
I find the wording of there a little confusing. Is the following
a correct rewrite:
The advantage of MS_STRICTATIME | MS_LAZYTIME is that stat(2)
will return the correctly updated atime, but the atime updates
will be flushed to disk only when (1) the inode needs to be
updated for filesystem / data consistency reasons or (2) the
inode is pushed out of memory, or (3) the filesystem is
unmounted.)
?
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>, Eric Sandeen <sandeen@redhat.com>
Cc: linux-man@vger.kernel.org, Linux API <linux-api@vger.kernel.org>,
XFS Developers <xfs@oss.sgi.com>,
mtk.manpages@gmail.com,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Linux btrfs Developers List <linux-btrfs@vger.kernel.org>
Subject: Re: Documenting MS_LAZYTIME
Date: Thu, 26 Feb 2015 09:49:39 +0100 [thread overview]
Message-ID: <54EEDE23.6080009@gmail.com> (raw)
In-Reply-To: <20150221025636.GB7922@thunk.org>
Ted,
On 02/21/2015 03:56 AM, Theodore Ts'o wrote:
> On Fri, Feb 20, 2015 at 09:49:34AM -0600, Eric Sandeen wrote:
>>
>>> This mount option significantly reduces writes to the
>>> inode table for workloads that perform frequent random
>>> writes to preallocated files.
>>
>> This seems like an overly specific description of a single workload out
>> of many which may benefit, but what do others think? "inode table" is also
>> fairly extN-specific.
>
> How about somethign like "This mount significantly reduces writes
> needed to update the inode's timestamps, especially mtime and actime.
What is "actime" in the preceding line? Should it be "ctime"?
> Examples of workloads where this could be a large win include frequent
> random writes to preallocated files, as well as cases where the
> MS_STRICTATIME mount option is enabled."?
I think some version of the following text could also usefully go
into the page, but...
> (The advantage of MS_STRICTATIME | MS_LAZYTIME is that stat system
> calls will return the correctly updated atime, but those atime updates
> won't get flushed to disk unless the inode needs to be updated for
> file system / data consistency reasons, or when the inode is pushed
> out of memory, or when the file system is unmounted.)
I find the wording of there a little confusing. Is the following
a correct rewrite:
The advantage of MS_STRICTATIME | MS_LAZYTIME is that stat(2)
will return the correctly updated atime, but the atime updates
will be flushed to disk only when (1) the inode needs to be
updated for filesystem / data consistency reasons or (2) the
inode is pushed out of memory, or (3) the filesystem is
unmounted.)
?
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-02-26 8:49 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 8:50 Documenting MS_LAZYTIME Michael Kerrisk
2015-02-20 8:50 ` Michael Kerrisk
2015-02-20 8:50 ` Michael Kerrisk
[not found] ` <CAHO5Pa0k7QkV_6BDjwTVxa7LV9tFyN9nGFFcSvOC6HYO08wfrw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-20 12:32 ` Andreas Dilger
2015-02-20 12:32 ` Andreas Dilger
2015-02-20 12:32 ` Andreas Dilger
2015-02-20 13:22 ` Michael Kerrisk (man-pages)
2015-02-20 13:22 ` Michael Kerrisk (man-pages)
2015-02-20 13:22 ` Michael Kerrisk (man-pages)
2015-02-20 15:49 ` Eric Sandeen
2015-02-20 15:49 ` Eric Sandeen
2015-02-20 15:49 ` Eric Sandeen
2015-02-21 2:56 ` Theodore Ts'o
2015-02-21 2:56 ` Theodore Ts'o
[not found] ` <20150221025636.GB7922-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2015-02-23 12:20 ` Austin S Hemmelgarn
2015-02-23 12:20 ` Austin S Hemmelgarn
2015-02-23 12:20 ` Austin S Hemmelgarn
[not found] ` <54EB1B19.8050808-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-23 16:24 ` Eric Sandeen
2015-02-23 16:24 ` Eric Sandeen
2015-02-23 16:24 ` Eric Sandeen
2015-02-26 8:53 ` Michael Kerrisk (man-pages)
2015-02-26 8:53 ` Michael Kerrisk (man-pages)
2015-02-26 8:49 ` Michael Kerrisk (man-pages) [this message]
2015-02-26 8:49 ` Michael Kerrisk (man-pages)
2015-02-26 8:49 ` Michael Kerrisk (man-pages)
2015-02-26 13:31 ` Theodore Ts'o
2015-02-26 13:31 ` Theodore Ts'o
2015-02-26 13:36 ` Michael Kerrisk (man-pages)
2015-02-26 13:36 ` Michael Kerrisk (man-pages)
2015-02-27 0:04 ` Theodore Ts'o
2015-02-27 0:04 ` Theodore Ts'o
[not found] ` <20150227000409.GC17174-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2015-02-27 8:01 ` Michael Kerrisk (man-pages)
2015-02-27 8:01 ` Michael Kerrisk (man-pages)
2015-02-27 8:01 ` Michael Kerrisk (man-pages)
[not found] ` <54F02446.2050008-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-27 8:08 ` Omar Sandoval
2015-02-27 8:08 ` Omar Sandoval
2015-02-27 8:08 ` Omar Sandoval
2015-02-27 8:36 ` Michael Kerrisk (man-pages)
2015-02-27 8:36 ` Michael Kerrisk (man-pages)
2015-02-27 8:36 ` Michael Kerrisk (man-pages)
[not found] ` <54F02C73.5090601-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-27 14:18 ` Theodore Ts'o
2015-02-27 14:18 ` Theodore Ts'o
2015-02-27 14:18 ` Theodore Ts'o
2015-02-27 17:51 ` Darrick J. Wong
2015-02-27 17:51 ` Darrick J. Wong
[not found] ` <20150227175159.GC11031-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2015-03-03 7:14 ` Michael Kerrisk (man-pages)
2015-03-03 7:14 ` Michael Kerrisk (man-pages)
2015-03-03 7:14 ` Michael Kerrisk (man-pages)
2015-02-21 7:57 ` Michael Kerrisk (man-pages)
2015-02-21 7:57 ` Michael Kerrisk (man-pages)
2015-02-22 18:30 ` Robert White
2015-02-22 18:30 ` Robert White
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=54EEDE23.6080009@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=tytso-3s7WtUTddSA@public.gmane.org \
--cc=xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.