[REVIEW 2/2] - setting realtime and extent size hint flags via fcntl(XFS_IOC_FSSETXATTR)

[Vlad Apostolov <vapo@sgi.com>]

[-- Attachment #1: Type: text/plain, Size: 105 bytes --]

This patch updates the xfsctl(XFS_IOC_FSSETXATTR) and 
xfsctl(XFS_IOC_RESVSP64)
man page.

Regards,
Vlad

[-- Attachment #2: update_XFS_IOC_FSSETXATTR_and_XFS_IOC_RESVSP64_xfsctl_man_page --]
[-- Type: text/plain, Size: 1546 bytes --]

Index: xfs-cmds/xfsprogs/man/man3/xfsctl.3
===================================================================
--- xfs-cmds.orig/xfsprogs/man/man3/xfsctl.3
+++ xfs-cmds/xfsprogs/man/man3/xfsctl.3
@@ -251,11 +251,17 @@ and
 .BR fsx_extsize .
 The
 .B fsx_xflags
-realtime file bit and the file's extent size may be changed only
+realtime file bit
+.B XFS_XFLAG_REALTIME,
+extent hint bit
+.B XFS_XFLAG_EXTSIZE
+and the file's extent size may be changed only
 when the file is empty, except in the case of a directory where
 the extent size can be set at any time (this value is only used
 for regular file allocations, so should only be set on a directory
 in conjunction with the XFS_XFLAG_EXTSZINHERIT flag).
+The extent size has to be aligned to the filesystem block size or
+when the XFS_XFLAG_REALTIME flag is set to the realtime extent size.
 
 .TP
 .B XFS_IOC_GETBMAP
@@ -325,7 +331,15 @@ The blocks are allocated, but not zeroed
 If the XFS filesystem is configured to flag unwritten file extents,
 performance will be negatively affected when writing to preallocated space,
 since extra filesystem transactions are required to convert extent flags on
-the range of the file written.
+the range of the file written. The
+.B l_len
+field is rounded to the filesystem block size.
+For realtime files the
+.B l_len
+field is rounded to the realtime extent size. If the extent hint is set, the
+.B l_len
+is rounded to the extent hint size.
+
 If
 .IR xfs_info (8)
 reports unwritten=1, then the filesystem was made to flag unwritten extents.