On Fri, Jan 28, 2022 at 03:39:35PM -0800, Eric Biggers wrote:
> [Note: I'm planning to send a patchset adding STATX_DIRECTIO as was
> discussed on v10, but that will be a separate patchset.]
>
> Encrypted files traditionally haven't supported DIO, due to the need to
> encrypt/decrypt the data. Ho
This patchset makes the statx() system call return I/O alignment
information, roughly following the design that was suggested at
https://lore.kernel.org/linux-fsdevel/[email protected]/T/#u
This feature solves two problems: (a) it allows userspace to determine
when a file
From: Eric Biggers
Traditionally, the conditions for when DIO (direct I/O) is supported
were fairly simple: filesystems either supported DIO aligned to the
block device's logical block size, or didn't support DIO at all.
However, due to filesystem features that have been added over time (e.g,
da
From: Eric Biggers
f2fs_force_buffered_io() is only used in file.c, so move it into there.
No behavior change. This makes it easier to review later patches.
Signed-off-by: Eric Biggers
---
fs/f2fs/f2fs.h | 45 -
fs/f2fs/file.c | 45 +
From: Eric Biggers
Currently, if an f2fs filesystem is mounted with the mode=lfs and
io_bits mount options, DIO reads are allowed but DIO writes are not.
Allowing DIO reads but not DIO writes is an unusual restriction, which
is likely to be surprising to applications, namely any application that
From: Eric Biggers
Add support for STATX_IOALIGN to f2fs, so that I/O alignment information
is exposed to userspace in a consistent and easy-to-use way.
Signed-off-by: Eric Biggers
---
fs/f2fs/file.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/fs/f2fs/f
From: Eric Biggers
Add support for STATX_IOALIGN to ext4, so that I/O alignment information
is exposed to userspace in a consistent and easy-to-use way.
Signed-off-by: Eric Biggers
---
fs/ext4/ext4.h | 1 +
fs/ext4/file.c | 15 ---
fs/ext4/inode.c | 31 ++
From: Eric Biggers
To prepare for STATX_IOALIGN support, make two changes to
fscrypt_dio_supported().
First, remove the filesystem-block-alignment check and make the
filesystems handle it instead. It previously made sense to have it in
fs/crypto/; however, to support STATX_IOALIGN the alignment
From: Eric Biggers
f2fs only allows direct I/O that is aligned to the filesystem block
size. Given that fact, simplify f2fs_force_buffered_io() by removing
the redundant call to block_unaligned_IO().
This makes it easier to reuse this code for STATX_IOALIGN.
Signed-off-by: Eric Biggers
---
f
On Thu, 10 Feb 2022, Jan Kara wrote:
> Hi Neil!
>
> On Thu 10-02-22 16:37:52, NeilBrown wrote:
> > Add some "big-picture" documentation for read-ahead and polish the code
> > to make it fit this documentation.
> >
> > The meaning of ->async_size is clarified to match its name.
> > i.e. Any reques
Hi Neil!
On Thu 10-02-22 16:37:52, NeilBrown wrote:
> Add some "big-picture" documentation for read-ahead and polish the code
> to make it fit this documentation.
>
> The meaning of ->async_size is clarified to match its name.
> i.e. Any request to ->readahead() has a sync part and an async part.
On Thu 10-02-22 16:37:52, NeilBrown wrote:
> bfq_get_queue() expects a "bool" for the third arg, so pass "false"
> rather than "BLK_RW_ASYNC" which will soon be removed.
>
> Acked-by: Jens Axboe
> Signed-off-by: NeilBrown
Looks good. Feel free to add:
Reviewed-by: Jan Kara
12 matches
Mail list logo
