From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, linux-api@vger.kernel.org,
linux-fscrypt@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 1/9] statx: add direct I/O alignment information
Date: Fri, 22 Jul 2022 13:31:37 -0400 [thread overview]
Message-ID: <yq1fsitjbqn.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20220722071228.146690-2-ebiggers@kernel.org> (Eric Biggers's message of "Fri, 22 Jul 2022 00:12:20 -0700")
Eric,
> Therefore, let's expose this information via statx(). Add the
> STATX_DIOALIGN flag and two new statx fields associated with it:
>
> * stx_dio_mem_align: the alignment (in bytes) required for user memory
> buffers for DIO, or 0 if DIO is not supported on the file.
>
> * stx_dio_offset_align: the alignment (in bytes) required for file
> offsets and I/O segment lengths for DIO, or 0 if DIO is not supported
> on the file. This will only be nonzero if stx_dio_mem_align is
> nonzero, and vice versa.
Nice to finally have a generic interface for this!
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-block@vger.kernel.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [f2fs-dev] [PATCH v4 1/9] statx: add direct I/O alignment information
Date: Fri, 22 Jul 2022 13:31:37 -0400 [thread overview]
Message-ID: <yq1fsitjbqn.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20220722071228.146690-2-ebiggers@kernel.org> (Eric Biggers's message of "Fri, 22 Jul 2022 00:12:20 -0700")
Eric,
> Therefore, let's expose this information via statx(). Add the
> STATX_DIOALIGN flag and two new statx fields associated with it:
>
> * stx_dio_mem_align: the alignment (in bytes) required for user memory
> buffers for DIO, or 0 if DIO is not supported on the file.
>
> * stx_dio_offset_align: the alignment (in bytes) required for file
> offsets and I/O segment lengths for DIO, or 0 if DIO is not supported
> on the file. This will only be nonzero if stx_dio_mem_align is
> nonzero, and vice versa.
Nice to finally have a generic interface for this!
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-07-22 17:32 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 7:12 [PATCH v4 0/9] make statx() return DIO alignment information Eric Biggers
2022-07-22 7:12 ` [f2fs-dev] " Eric Biggers
2022-07-22 7:12 ` [PATCH v4 1/9] statx: add direct I/O " Eric Biggers
2022-07-22 7:12 ` [f2fs-dev] " Eric Biggers
2022-07-22 16:32 ` Darrick J. Wong
2022-07-22 16:32 ` [f2fs-dev] " Darrick J. Wong
2022-07-22 17:31 ` Martin K. Petersen [this message]
2022-07-22 17:31 ` Martin K. Petersen
2022-07-22 7:12 ` [PATCH v4 2/9] vfs: support STATX_DIOALIGN on block devices Eric Biggers
2022-07-22 7:12 ` [f2fs-dev] " Eric Biggers
2022-07-22 8:10 ` Christoph Hellwig
2022-07-22 8:10 ` [f2fs-dev] " Christoph Hellwig
2022-07-22 17:32 ` Martin K. Petersen
2022-07-22 17:32 ` [f2fs-dev] " Martin K. Petersen
2022-07-22 7:12 ` [PATCH v4 3/9] fscrypt: change fscrypt_dio_supported() to prepare for STATX_DIOALIGN Eric Biggers
2022-07-22 7:12 ` [f2fs-dev] " Eric Biggers
2022-07-22 8:10 ` Christoph Hellwig
2022-07-22 8:10 ` [f2fs-dev] " Christoph Hellwig
2022-07-22 7:12 ` [PATCH v4 4/9] ext4: support STATX_DIOALIGN Eric Biggers
2022-07-22 7:12 ` [f2fs-dev] " Eric Biggers
2022-07-22 17:05 ` Theodore Ts'o
2022-07-22 17:05 ` [f2fs-dev] " Theodore Ts'o
2022-07-22 7:12 ` [PATCH v4 5/9] f2fs: move f2fs_force_buffered_io() into file.c Eric Biggers
2022-07-22 7:12 ` [f2fs-dev] " Eric Biggers
2022-07-22 7:12 ` [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes Eric Biggers
2022-07-22 7:12 ` [f2fs-dev] " Eric Biggers
2022-07-24 2:01 ` Jaegeuk Kim
2022-07-24 2:01 ` [f2fs-dev] " Jaegeuk Kim
2022-07-25 18:12 ` Eric Biggers
2022-07-25 18:12 ` [f2fs-dev] " Eric Biggers
2022-07-25 23:58 ` Andreas Dilger
2022-07-31 3:08 ` Jaegeuk Kim
2022-07-31 3:08 ` [f2fs-dev] " Jaegeuk Kim
2022-08-16 0:55 ` Eric Biggers
2022-08-16 0:55 ` Eric Biggers
2022-08-16 9:03 ` [f2fs-dev] " Dave Chinner
2022-08-16 9:03 ` Dave Chinner
2022-08-16 16:42 ` Andreas Dilger
2022-08-19 23:09 ` Eric Biggers
2022-08-19 23:09 ` [f2fs-dev] " Eric Biggers
2022-08-23 3:22 ` Andreas Dilger
2022-08-20 0:06 ` Jaegeuk Kim
2022-08-20 0:06 ` [f2fs-dev] " Jaegeuk Kim
2022-08-20 0:33 ` Eric Biggers
2022-08-20 0:33 ` Eric Biggers
2022-08-21 8:53 ` Christoph Hellwig
2022-08-21 8:53 ` [f2fs-dev] " Christoph Hellwig
2022-07-22 7:12 ` [PATCH v4 7/9] f2fs: simplify f2fs_force_buffered_io() Eric Biggers
2022-07-22 7:12 ` [f2fs-dev] " Eric Biggers
2022-07-22 7:12 ` [PATCH v4 8/9] f2fs: support STATX_DIOALIGN Eric Biggers
2022-07-22 7:12 ` [f2fs-dev] " Eric Biggers
2022-07-22 7:12 ` [PATCH v4 9/9] xfs: " Eric Biggers
2022-07-22 7:12 ` [f2fs-dev] " Eric Biggers
2022-07-22 8:11 ` Christoph Hellwig
2022-07-22 8:11 ` [f2fs-dev] " Christoph Hellwig
2022-07-22 16:24 ` Darrick J. Wong
2022-07-22 16:24 ` [f2fs-dev] " Darrick J. Wong
2022-08-26 17:19 ` [PATCH v4 0/9] make statx() return DIO alignment information Jeff Layton
2022-08-26 17:19 ` [f2fs-dev] " Jeff Layton
2022-08-27 7:07 ` Eric Biggers
2022-08-27 7:07 ` [f2fs-dev] " Eric Biggers
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=yq1fsitjbqn.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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.