From: sat <takeuchi_satoru@jp.fujitsu.com>
To: xfs@oss.sgi.com, Rob Landley <rob@landley.net>,
Dave Chinner <david@fromorbit.com>
Subject: [PATCH] XFS: fix the description of 'allocsize=' mount option
Date: Mon, 24 Feb 2014 15:04:21 +0900 [thread overview]
Message-ID: <530AE0E5.1090707@jp.fujitsu.com> (raw)
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
The end-of-file preallocation size is dynamic by default.
So the description about the default size of preallocation
should be removed.
Instead, adding the description about the initial size of
dynamic preallocation is useful for users.
Signed-off-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Cc: Dave Chinner <david@fromorbit.com>
Cc: Rob Landley <rob@landley.net>
---
Documentation/filesystems/xfs.txt | 16 ++++++++--------
1 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/Documentation/filesystems/xfs.txt b/Documentation/filesystems/xfs.txt
index 5be51fd..30e57b0 100644
--- a/Documentation/filesystems/xfs.txt
+++ b/Documentation/filesystems/xfs.txt
@@ -23,16 +23,16 @@ default behaviour.
allocsize=size
Sets the buffered I/O end-of-file preallocation size when
- doing delayed allocation writeout (default size is 64KiB).
- Valid values for this option are page size (typically 4KiB)
- through to 1GiB, inclusive, in power-of-2 increments.
+ doing delayed allocation writeout. Valid values for this
+ option are page size (typically 4KiB) through to 1GiB,
+ inclusive, in power-of-2 increments.
The default behaviour is for dynamic end-of-file
- preallocation size, which uses a set of heuristics to
- optimise the preallocation size based on the current
- allocation patterns within the file and the access patterns
- to the file. Specifying a fixed allocsize value turns off
- the dynamic behaviour.
+ preallocation size (initial size is 64KiB), which uses a
+ set of heuristics to optimise the preallocation size based
+ on the current allocation patterns within the file and
+ the access patterns to the file. Specifying a fixed
+ allocsize value turns off the dynamic behaviour.
attr2
noattr2
--
1.7.1
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-02-24 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 6:04 sat [this message]
2014-02-24 12:06 ` [PATCH] XFS: fix the description of 'allocsize=' mount option Dave Chinner
2014-02-26 4:38 ` sat
2014-02-27 6:42 ` Dave Chinner
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=530AE0E5.1090707@jp.fujitsu.com \
--to=takeuchi_satoru@jp.fujitsu.com \
--cc=david@fromorbit.com \
--cc=rob@landley.net \
--cc=xfs@oss.sgi.com \
/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