RWF_DONTCACHE documentation
Hi Jens,
I just tried to reference RWF_DONTCACHE semantics in a standards discussion, but it doesn't seem to be documented in the man pages or in fact anywhere else I could easily find. Could you please write up the semantics for the preadv2/pwritev2 man page?
Quoted 6 lines · Christoph Hellwig
Hi Jens,
I just tried to reference
RWF_DONTCACHEsemantics in a standards discussion, but it doesn't seem to be documented in the man pages or in fact anywhere else I could easily find. Could you please write up the semantics for the preadv2/pwritev2 man page?
Sure, I can write up something for the man page.
Signature · 1 line
Jens Axboe
Quoted 9 lines · Jens Axboe
Quoted 6 lines · Christoph Hellwig
Hi Jens,
I just tried to reference
RWF_DONTCACHEsemantics in a standards discussion, but it doesn't seem to be documented in the man pages or in fact anywhere else I could easily find. Could you please write up the semantics for the preadv2/pwritev2 man page?Sure, I can write up something for the man page.
Adding Darrick as well, as a) he helped review the patches, and b) his phrasing is usually much better than mine.
Anyway, here's my first attempt:
man/man2/readv.2 +28 -0
@@ -301,6 +301,28 @@ or their equivalent flags and system calls are used .B RWF_SYNC is specified for .BR pwritev2 ()). +.TP +.BR RWF_DONTCACHE " (since Linux 6.14)" +Reads or writes to a regular file will prune instantiated page cache content +when the operation completes. This is different than normal buffered I/O, +where the data usually remains in cache until such time that it gets reclaimed +due to memory pressure. If ranges of the read or written I/O was already in +cache before this read or write, then those range will not be pruned at I/O +completion time. Additionally, any range dirtied by a write operation with +.B RWF_DONTCACHE +set will get kicked off for writeback. This is similar to calling +.BR sync_file_range (2) +with +.IR SYNC_FILE_RANGE_WRITE +to start writeback on the given range. +.B RWF_DONTCACHE +is a hint, or best effort, where no hard guarantees are given on the state of +the page cache once the operation completes. Note: file systems must support +this feature as well. If used on a file system or block device that doesn't +support it will return \-1 and +.I errno +will be set to +.B EOPNOTSUPP . .SH RETURN VALUE On success, .BR readv (),
@@ -368,6 +390,12 @@ value from .I statx. .TP .B EOPNOTSUPP +.B RWF_DONTCACHE +was set in +.IR flags +and the file doesn't support it. +.TP +.B EOPNOTSUPP An unknown flag is specified in .IR flags . .SH VERSIONS
Signature · 1 line
Jens Axboe
Alejandro Colomar
maintainerHi Jens,
Quoted 21 lines · Jens Axboe
Quoted 9 lines · Jens Axboe
Quoted 6 lines · Christoph Hellwig
Hi Jens,
I just tried to reference
RWF_DONTCACHEsemantics in a standards discussion, but it doesn't seem to be documented in the man pages or in fact anywhere else I could easily find. Could you please write up the semantics for the preadv2/pwritev2 man page?Sure, I can write up something for the man page.
Adding Darrick as well, as a) he helped review the patches, and b) his phrasing is usually much better than mine.
Anyway, here's my first attempt:
man/man2/readv.2 +0
-0
man/man2/readv.2 or their equivalent flags and system calls are used · line 307
Quoted 7 lines
man/man2/readv.2 +4
-0@@ -301,6 +301,28 @@ or their equivalent flags and system calls are used .B RWF_SYNC is specified for .BR pwritev2 ()). +.TP +.BR RWF_DONTCACHE " (since Linux 6.14)" +Reads or writes to a regular file will prune instantiated page cache content +when the operation completes. This is different than normal buffered I/O,
Please use semantic newlines, even for drafts; it makes editing later much easier. See man-pages(7):
$ MANWIDTH=72 man man-pages | sed -n '/Use semantic newlines/,/^$/p'
Use semantic newlines
In the source of a manual page, new sentences should be started on
new lines, long sentences should be split into lines at clause
breaks (commas, semicolons, colons, and so on), and long clauses
should be split at phrase boundaries. This convention, sometimes
known as "semantic newlines", makes it easier to see the effect of
patches, which often operate at the level of individual sentences,
clauses, or phrases.And a quote from Brian W. Kernighan about preparing documents:
Brian W. Kernighan, 1974 [UNIX For Beginners]:
[
Hints for Preparing Documents
Most documents go through several versions
(always more than you expected)
before they are finally finished.
Accordingly,
you should do whatever possible
to make the job of changing them easy.
First,
when you do the purely mechanical operations of typing, type so subsequent editing will be easy.
Start each sentence on a new line.
Make lines short,
and break lines at natural places,
such as after commas and semicolons,
rather than randomly.
Since most people change documents
by rewriting phrases and
adding, deleting and rearranging sentences,
these precautions simplify any editing you have to do later. ]
man/man2/readv.2 or their equivalent flags and system calls are used · line 309
Quoted 2 lines
man/man2/readv.2 +2
-0+where the data usually remains in cache until such time that it gets reclaimed +due to memory pressure. If ranges of the read or written I/O was already in
s/was/were/
man/man2/readv.2 or their equivalent flags and system calls are used · line 310
Quoted 1 line
man/man2/readv.2 +1
-0+cache before this read or write, then those range will not be pruned at I/O
s/range/&s/
Quoted 4 lines
man/man2/readv.2 +4
-0+completion time. Additionally, any range dirtied by a write operation with +.B RWF_DONTCACHE +set will get kicked off for writeback. This is similar to calling +.BR sync_file_range (2)
man/man2/readv.2 or their equivalent flags and system calls are used
Quoted 10 lines
man/man2/readv.2 +8
-0+with +.IR SYNC_FILE_RANGE_WRITE +to start writeback on the given range. +.B RWF_DONTCACHE +is a hint, or best effort, where no hard guarantees are given on the state of +the page cache once the operation completes. +Note: file systems must support +this feature as well.
I'd remove the sentence above. It's redundant with the following one. Also, to give it more visibility, and because it's not connected with the preceding text, I'd move it to a new paragraph with '.IP'.
Other than this comments, the text looks good to me. Thanks!
Have a lovely day!
Alex
Quoted 25 lines
man/man2/readv.2 +11
-0+If used on a file system or block device that doesn't +support it will return \-1 and +.I errno +will be set to +.B EOPNOTSUPP . .SH RETURN VALUE On success, .BR readv (),@@ -368,6 +390,12 @@ value from .I statx. .TP .B EOPNOTSUPP +.B RWF_DONTCACHE +was set in +.IR flags +and the file doesn't support it. +.TP +.B EOPNOTSUPP An unknown flag is specified in .IR flags . .SH VERSIONSSignature · 2 lines
-- Jens Axboe
Signature · 1 line
<https://www.alejandro-colomar.es/>
Quoted 95 lines
Hi Jens,
Quoted 21 lines · Jens Axboe
Quoted 9 lines · Jens Axboe
Quoted 6 lines · Christoph Hellwig
Hi Jens,
I just tried to reference
RWF_DONTCACHEsemantics in a standards discussion, but it doesn't seem to be documented in the man pages or in fact anywhere else I could easily find. Could you please write up the semantics for the preadv2/pwritev2 man page?Sure, I can write up something for the man page.
Adding Darrick as well, as a) he helped review the patches, and b) his phrasing is usually much better than mine.
Anyway, here's my first attempt:
man/man2/readv.2 +0
-0man/man2/readv.2 or their equivalent flags and system calls are used · line 307
Quoted 7 lines
man/man2/readv.2 +4
-0@@ -301,6 +301,28 @@ or their equivalent flags and system calls are used .B RWF_SYNC is specified for .BR pwritev2 ()). +.TP +.BR RWF_DONTCACHE " (since Linux 6.14)" +Reads or writes to a regular file will prune instantiated page cache content +when the operation completes. This is different than normal buffered I/O,Please use semantic newlines, even for drafts; it makes editing later much easier. See man-pages(7):
$ MANWIDTH=72 man man-pages | sed -n '/Use semantic newlines/,/^$/p' Use semantic newlines In the source of a manual page, new sentences should be started on new lines, long sentences should be split into lines at clause breaks (commas, semicolons, colons, and so on), and long clauses should be split at phrase boundaries. This convention, sometimes known as "semantic newlines", makes it easier to see the effect of patches, which often operate at the level of individual sentences, clauses, or phrases.And a quote from Brian W. Kernighan about preparing documents:
Brian W. Kernighan, 1974 [UNIX For Beginners]:
[
Hints for Preparing DocumentsMost documents go through several versions
(always more than you expected)
before they are finally finished.
Accordingly,
you should do whatever possible
to make the job of changing them easy.First,
when you do the purely mechanical operations of typing, type so subsequent editing will be easy.
Start each sentence on a new line.
Make lines short,
and break lines at natural places,
such as after commas and semicolons,
rather than randomly.
Since most people change documents
by rewriting phrases and
adding, deleting and rearranging sentences,
these precautions simplify any editing you have to do later. ]man/man2/readv.2 or their equivalent flags and system calls are used · line 309
Quoted 2 lines
man/man2/readv.2 +2
-0+where the data usually remains in cache until such time that it gets reclaimed +due to memory pressure. If ranges of the read or written I/O was already ins/was/were/
man/man2/readv.2 or their equivalent flags and system calls are used · line 310
Quoted 1 line
man/man2/readv.2 +1
-0+cache before this read or write, then those range will not be pruned at I/Os/range/&s/
Quoted 10 lines
man/man2/readv.2 +10
-0+completion time. Additionally, any range dirtied by a write operation with +.B RWF_DONTCACHE +set will get kicked off for writeback. This is similar to calling +.BR sync_file_range (2) +with +.IR SYNC_FILE_RANGE_WRITE +to start writeback on the given range. +.B RWF_DONTCACHE +is a hint, or best effort, where no hard guarantees are given on the state of +the page cache once the operation completes.
Quoted 8 lines
man/man2/readv.2 or their equivalent flags and system calls are used · line 322
Quoted 2 lines
man/man2/readv.2 +2
-0+Note: file systems must support +this feature as well.I'd remove the sentence above. It's redundant with the following one. Also, to give it more visibility, and because it's not connected with the preceding text, I'd move it to a new paragraph with '.IP'.
Other than this comments, the text looks good to me. Thanks!
I kind of walked away from this one as I didn't have time or motivation to push it forward. FWIW, if you want to massage it into submission that'd be greatly appreciated. I'm not a regular man page contributor nor do I aim to be, but I do feel like we should this feature documented.
Signature · 1 line
Jens Axboe
Alejandro Colomar
maintainerHi Jens,
Quoted 7 lines · Jens Axboe
Quoted 1 line
Other than this comments, the text looks good to me. Thanks!
I kind of walked away from this one as I didn't have time or motivation to push it forward. FWIW, if you want to massage it into submission that'd be greatly appreciated. I'm not a regular man page contributor nor do I aim to be, but I do feel like we should this feature documented.
I understand your lack of interest in writing quality man(7) source code if that means iterations of patches. However, you may find the build system helpful to find some of the most obvious mistakes by yourself. This might help you in future patches.
$ make lint-man build-all -R TROFF .tmp/man/man2/readv.2.cat.set an.tmac:.tmp/man/man2/readv.2:316: style: .IR expects at least 2 arguments, got 1 an.tmac:.tmp/man/man2/readv.2:395: style: .IR expects at least 2 arguments, got 1 make: *** [/srv/alx/src/linux/man-pages/man-pages/contrib/share/mk/build/catman/troff.mk:66: .tmp/man/man2/readv.2.cat.set] Error 1 make: *** Deleting file '.tmp/man/man2/readv.2.cat.set'
Here's a diff with all the issues I raised fixed. Please add a commit message, and I'll apply it.
Have a lovely day!
Alex
man/man2/readv.2 +39 -0
@@ -301,6 +301,39 @@ .SS preadv2() and pwritev2() .B RWF_SYNC is specified for .BR pwritev2 ()). +.TP +.BR RWF_DONTCACHE " (since Linux 6.14)" +Reads or writes to a regular file +will prune instantiated page cache content +when the operation completes. +This is different than normal buffered I/O, +where the data usually remains in cache +until such time that it gets reclaimed +due to memory pressure. +If ranges of the read or written I/O +were already in cache before this read or write, +then those ranges will not be pruned at I/O completion time. +.IP +Additionally, +any range dirtied by a write operation with +.B RWF_DONTCACHE +set will get kicked off for writeback. +This is similar to calling +.BR sync_file_range (2) +with +.I SYNC_FILE_RANGE_WRITE +to start writeback on the given range. +.B RWF_DONTCACHE +is a hint, or best effort, +where no hard guarantees are given on the state of the page cache +once the operation completes. +.IP +If used on a file system or block device +that doesn't support it, +it will return \-1, and +.I errno +will be set to +.BR EOPNOTSUPP . .SH RETURN VALUE On success, .BR readv (),
@@ -368,6 +401,12 @@ .SH ERRORS .I statx. .TP .B EOPNOTSUPP +.B RWF_DONTCACHE +was set in +.I flags +and the file doesn't support it. +.TP +.B EOPNOTSUPP An unknown flag is specified in .IR flags . .SH VERSIONS
Quoted 4 lines
Signature · 2 lines
-- Jens Axboe
Signature · 1 line
<https://www.alejandro-colomar.es/>
Quoted 5 lines · Alejandro Colomar
Hi Jens,
Quoted 2 lines · Jens Axboe
Quoted 1 line
Other than this comments, the text looks good to me. Thanks!
Quoted 8 lines
Quoted 5 lines
I kind of walked away from this one as I didn't have time or motivation to push it forward. FWIW, if you want to massage it into submission that'd be greatly appreciated. I'm not a regular man page contributor nor do I aim to be, but I do feel like we should this feature documented.
I understand your lack of interest in writing quality man(7) source code if that means iterations of patches. However, you may find the build
It's not really lack of interest, it's just that there's only so much time and the idea of a back and forth on documentation isn't high on the list :-)
Quoted 9 lines
system helpful to find some of the most obvious mistakes by yourself. This might help you in future patches.
$ make lint-man build-all -R TROFF .tmp/man/man2/readv.2.cat.set an.tmac:.tmp/man/man2/readv.2:316: style: .IR expects at least 2 arguments, got 1 an.tmac:.tmp/man/man2/readv.2:395: style: .IR expects at least 2 arguments, got 1 make: *** [/srv/alx/src/linux/man-pages/man-pages/contrib/share/mk/build/catman/troff.mk:66: .tmp/man/man2/readv.2.cat.set] Error 1 make: *** Deleting file '.tmp/man/man2/readv.2.cat.set'
I'll remember for next time!
Quoted 2 lines
Here's a diff with all the issues I raised fixed. Please add a commit message, and I'll apply it.
Beautiful, thank you! Maybe paste the same section into writev.2 as well? For commit message, something ala
man/man2/readv.2: document RWF_DONTCACHE
Add a description of the RWF_DONTCACHE IO flag, which tells the kernel that any page cache instantiated by this IO, should be dropped when the operation has completed.
?
Signature · 1 line
Jens Axboe
Alejandro Colomar
maintainerPATCH v2 1/1 man/man2/readv.2: Document RWF_DONTCACHE
Add a description of the RWF_DONTCACHE IO flag, which tells the kernel that any page cache instantiated by this IO, should be dropped when the operation has completed.
---
Hi Jens,
Here's the patch. We don't need to paste it into writev(2), because writev(2) is documented in readv(2); they're the same page.
Thanks for the commit message!
Please sign it, if you like it.
Have a lovely day!
Alex
man/man2/readv.2 | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+)
man/man2/readv.2 +39 -0
@@ -301,6 +301,39 @@ .SS preadv2() and pwritev2() .B RWF_SYNC is specified for .BR pwritev2 ()). +.TP +.BR RWF_DONTCACHE " (since Linux 6.14)" +Reads or writes to a regular file +will prune instantiated page cache content +when the operation completes. +This is different than normal buffered I/O, +where the data usually remains in cache +until such time that it gets reclaimed +due to memory pressure. +If ranges of the read or written I/O +were already in cache before this read or write, +then those ranges will not be pruned at I/O completion time. +.IP +Additionally, +any range dirtied by a write operation with +.B RWF_DONTCACHE +set will get kicked off for writeback. +This is similar to calling +.BR sync_file_range (2) +with +.I SYNC_FILE_RANGE_WRITE +to start writeback on the given range. +.B RWF_DONTCACHE +is a hint, or best effort, +where no hard guarantees are given on the state of the page cache +once the operation completes. +.IP +If used on a file system or block device +that doesn't support it, +it will return \-1, and +.I errno +will be set to +.BR EOPNOTSUPP . .SH RETURN VALUE On success, .BR readv (),
@@ -368,6 +401,12 @@ .SH ERRORS .I statx. .TP .B EOPNOTSUPP +.B RWF_DONTCACHE +was set in +.I flags +and the file doesn't support it. +.TP +.B EOPNOTSUPP An unknown flag is specified in .IR flags . .SH VERSIONS
Range-diff against v1:
-: --------- > 1: 9e1f1b2d6 man/man2/readv.2: Document RWF_DONTCACHE
base-commit: aa88bcfabc52b7d4ef52a8e5a4be0260676d81bc
prerequisite-patch-id: b91cde16f48eeae2a44bae89e8cbb41d9034a865
prerequisite-patch-id: 0c0617b91c32758d64e6e8b2f8ddd434199d842b
prerequisite-patch-id: 02385b38b2a5ec5c04a468e888b1bc14aace9ec6
prerequisite-patch-id: 10e6a0e6e2edd5e74767af533958389454f72ab5
prerequisite-patch-id: 2dc3d94ce9d6e965182437c822479f55ec67da07
prerequisite-patch-id: 9e5fef3be8cc4d5d2828c415cf5a923e055640fc
prerequisite-patch-id: 3de1fc513b71447bb13ac740474138c80e3a463e
Signature · 1 line
2.50.1
Alejandro Colomar
maintainerRe: [PATCH v2] man/man2/readv.2: Document RWF_DONTCACHE
Oops, I forgot to sent to linux-man@.
Quoted 102 lines · Alejandro Colomar
Add a description of the
RWF_DONTCACHEIO flag, which tells the kernel that any page cache instantiated by this IO, should be dropped when the operation has completed.Reported-by Christoph Hellwig <[email protected]>Cc "Darrick J. Wong" <[email protected]>Cc Johannes Thumshirn <[email protected]>Co-authored-by Jens Axboe <[email protected]>[alx: editorial improvements; srcfix, ffix]Signed-off-by Alejandro Colomar <[email protected]>---
Hi Jens,
Here's the patch. We don't need to paste it into writev(2), because writev(2) is documented in readv(2); they're the same page.
Thanks for the commit message!
Please sign it, if you like it.
Have a lovely day!
Alexman/man2/readv.2 | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+)man/man2/readv.2 +39
-0@@ -301,6 +301,39 @@ .SS preadv2() and pwritev2() .B RWF_SYNC is specified for .BR pwritev2 ()). +.TP +.BR RWF_DONTCACHE " (since Linux 6.14)" +Reads or writes to a regular file +will prune instantiated page cache content +when the operation completes. +This is different than normal buffered I/O, +where the data usually remains in cache +until such time that it gets reclaimed +due to memory pressure. +If ranges of the read or written I/O +were already in cache before this read or write, +then those ranges will not be pruned at I/O completion time. +.IP +Additionally, +any range dirtied by a write operation with +.B RWF_DONTCACHE +set will get kicked off for writeback. +This is similar to calling +.BR sync_file_range (2) +with +.I SYNC_FILE_RANGE_WRITE +to start writeback on the given range. +.B RWF_DONTCACHE +is a hint, or best effort, +where no hard guarantees are given on the state of the page cache +once the operation completes. +.IP +If used on a file system or block device +that doesn't support it, +it will return \-1, and +.I errno +will be set to +.BR EOPNOTSUPP . .SH RETURN VALUE On success, .BR readv (),@@ -368,6 +401,12 @@ .SH ERRORS .I statx. .TP .B EOPNOTSUPP +.B RWF_DONTCACHE +was set in +.I flags +and the file doesn't support it. +.TP +.B EOPNOTSUPP An unknown flag is specified in .IR flags . .SH VERSIONSRange-diff against v1:
-: --------- > 1:9e1f1b2d6man/man2/readv.2: DocumentRWF_DONTCACHEbase-commit:
aa88bcfabc52b7d4ef52a8e5a4be0260676d81bc
prerequisite-patch-id:b91cde16f48eeae2a44bae89e8cbb41d9034a865
prerequisite-patch-id:0c0617b91c32758d64e6e8b2f8ddd434199d842b
prerequisite-patch-id:02385b38b2a5ec5c04a468e888b1bc14aace9ec6
prerequisite-patch-id:10e6a0e6e2edd5e74767af533958389454f72ab5
prerequisite-patch-id:2dc3d94ce9d6e965182437c822479f55ec67da07
prerequisite-patch-id:9e5fef3be8cc4d5d2828c415cf5a923e055640fc
prerequisite-patch-id:3de1fc513b71447bb13ac740474138c80e3a463eSignature · 1 line
2.50.1
Signature · 2 lines
<https://www.alejandro-colomar.es> Use port 80 (that is, <...:80/>).
Re: [PATCH v2] man/man2/readv.2: Document RWF_DONTCACHE
In reply to Alejandro ColomarQuoted 13 lines · Alejandro Colomar
Add a description of the
RWF_DONTCACHEIO flag, which tells the kernel that any page cache instantiated by this IO, should be dropped when the operation has completed.Reported-by Christoph Hellwig <[email protected]>Cc "Darrick J. Wong" <[email protected]>Cc Johannes Thumshirn <[email protected]>Co-authored-by Jens Axboe <[email protected]>[alx: editorial improvements; srcfix, ffix]Signed-off-by Alejandro Colomar <[email protected]>---
Quoted 8 lines
Hi Jens,
Here's the patch. We don't need to paste it into writev(2), because writev(2) is documented in readv(2); they're the same page.
Thanks for the commit message!
Please sign it, if you like it.
Thanks for doing this!
Signature · 1 line
Jens Axboe
Alejandro Colomar
maintainerRe: [PATCH v2] man/man2/readv.2: Document RWF_DONTCACHE
Hi Jens,
Quoted 19 lines · Jens Axboe
Quoted 18 lines · Alejandro Colomar
Add a description of the
RWF_DONTCACHEIO flag, which tells the kernel that any page cache instantiated by this IO, should be dropped when the operation has completed.Reported-by Christoph Hellwig <[email protected]>Cc "Darrick J. Wong" <[email protected]>Cc Johannes Thumshirn <[email protected]>Co-authored-by Jens Axboe <[email protected]>[alx: editorial improvements; srcfix, ffix]Signed-off-by Alejandro Colomar <[email protected]>---
Hi Jens,
Here's the patch. We don't need to paste it into writev(2), because writev(2) is documented in readv(2); they're the same page.
Quoted 8 lines
Quoted 3 lines
Thanks for the commit message!
Please sign it, if you like it.
Thanks for doing this!
Signed-off-by Jens Axboe <[email protected]>
Thanks for the help! It seems I accidentally pushed the patch before appending this tag. :|
Have a lovely night!
Alex
Quoted 4 lines
Signature · 1 line
Jens Axboe
Signature · 2 lines
<https://www.alejandro-colomar.es> Use port 80 (that is, <...:80/>).
Re: [PATCH v2] man/man2/readv.2: Document RWF_DONTCACHE
In reply to Alejandro ColomarLooks good:
Alejandro Colomar
maintainerRe: [PATCH v2] man/man2/readv.2: Document RWF_DONTCACHE
Quoted 3 lines · Christoph Hellwig
Looks good:
Reviewed-by Christoph Hellwig <[email protected]>
Hi Chirstoph,
Thanks! For some reason, I accidentally pushed the patch without appending the review tags. :(
Have a lovely night!
Alex
Signature · 2 lines
<https://www.alejandro-colomar.es> Use port 80 (that is, <...:80/>).
Quoted 10 lines · Jens Axboe
Quoted 6 lines · Christoph Hellwig
Hi Jens,
I just tried to reference
RWF_DONTCACHEsemantics in a standards discussion, but it doesn't seem to be documented in the man pages or in fact anywhere else I could easily find. Could you please write up the semantics for the preadv2/pwritev2 man page?Sure, I can write up something for the man page.
Hi Jens,
Small sidetrack here. What happened to the ext4 and btrfs support of RWF_DONTCACHE? I remember seeing your series having ext4 and btrfs support as well but in current master only xfs is setting FOP_DONTCACHE.
What did I miss?
Thanks,
Johannes
Quoted 9 lines · Johannes Thumshirn
Quoted 8 lines · Jens Axboe
Quoted 6 lines · Christoph Hellwig
Hi Jens,
I just tried to reference
RWF_DONTCACHEsemantics in a standards discussion, but it doesn't seem to be documented in the man pages or in fact anywhere else I could easily find. Could you please write up the semantics for the preadv2/pwritev2 man page?
Quoted 8 lines
Quoted 2 lines
Sure, I can write up something for the man page.
Hi Jens,
Small sidetrack here. What happened to the ext4 and btrfs support of
RWF_DONTCACHE? I remember seeing your series having ext4 and btrfs support as well but in current master only xfs is settingFOP_DONTCACHE.
The btrfs support got queued up, that's all I know on that front. For ext4, it needed a bit of a hack [1] and there was some chatter on converting the write side to iomap, which would eliminate the need for that hack. The last fs patches I had on top of the core bits was:
https://git.kernel.dk/cgit/linux/log/?h=buffered-uncached-fs.11
in case you or someone else wants to pursue those parts.
Signature · 1 line
Jens Axboe
Quoted 24 lines · Jens Axboe
Quoted 9 lines · Johannes Thumshirn
Quoted 8 lines · Jens Axboe
Quoted 6 lines · Christoph Hellwig
Hi Jens,
I just tried to reference
RWF_DONTCACHEsemantics in a standards discussion, but it doesn't seem to be documented in the man pages or in fact anywhere else I could easily find. Could you please write up the semantics for the preadv2/pwritev2 man page?Quoted 8 lines
Quoted 2 lines
Sure, I can write up something for the man page.
Hi Jens,
Small sidetrack here. What happened to the ext4 and btrfs support of
RWF_DONTCACHE? I remember seeing your series having ext4 and btrfs support as well but in current master only xfs is settingFOP_DONTCACHE.The btrfs support got queued up, that's all I know on that front. For ext4, it needed a bit of a hack [1] and there was some chatter on converting the write side to iomap, which would eliminate the need for that hack. The last fs patches I had on top of the core bits was:
Quoted 6 lines
https://git.kernel.dk/cgit/linux/log/?h=buffered-uncached-fs.11
in case you or someone else wants to pursue those parts.
Thanks