public inbox for [email protected]
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <[email protected]>
To: Stefan Roesch <[email protected]>
Cc: [email protected], [email protected], [email protected],
	[email protected], [email protected],
	[email protected], [email protected], [email protected]
Subject: Re: [RFC PATCH v4 16/17] xfs: Add async buffered write support
Date: Sun, 22 May 2022 08:35:27 -0700	[thread overview]
Message-ID: <YopYP9vI7E7LbjiD@magnolia> (raw)
In-Reply-To: <[email protected]>

On Fri, May 20, 2022 at 11:36:45AM -0700, Stefan Roesch wrote:
> This adds the async buffered write support to XFS. For async buffered
> write requests, the request will return -EAGAIN if the ilock cannot be
> obtained immediately.
> 
> This splits off a new helper xfs_ilock_inode from the existing helper
> xfs_ilock_iocb so it can be used for this function. The exising helper
> cannot be used as it hardcoded the inode to be used.
> 
> Signed-off-by: Stefan Roesch <[email protected]>
> ---
>  fs/xfs/xfs_file.c | 32 +++++++++++++++-----------------
>  1 file changed, 15 insertions(+), 17 deletions(-)
> 
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index 793918c83755..ad3175b7d366 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -190,14 +190,13 @@ xfs_file_fsync(
>  	return error;
>  }
>  
> -static int
> -xfs_ilock_iocb(
> -	struct kiocb		*iocb,
> +static inline int
> +xfs_ilock_xfs_inode(

A couple of nitpicky things:

"ilock" is shorthand for "inode lock", which means this name expands to
"xfs inode lock xfs inode", which is redundant.  Seeing as the whole
point of this function is to take a particular inode lock with a
particular set of IOCB flags, just leave the name as it was.

> +	struct xfs_inode	*ip,
> +	int			flags,

"iocb_flags", not "flags", to reinforce what kind of flags are supposed
to be passed in here.

--D

>  	unsigned int		lock_mode)
>  {
> -	struct xfs_inode	*ip = XFS_I(file_inode(iocb->ki_filp));
> -
> -	if (iocb->ki_flags & IOCB_NOWAIT) {
> +	if (flags & IOCB_NOWAIT) {
>  		if (!xfs_ilock_nowait(ip, lock_mode))
>  			return -EAGAIN;
>  	} else {
> @@ -222,7 +221,7 @@ xfs_file_dio_read(
>  
>  	file_accessed(iocb->ki_filp);
>  
> -	ret = xfs_ilock_iocb(iocb, XFS_IOLOCK_SHARED);
> +	ret = xfs_ilock_xfs_inode(ip, iocb->ki_flags, XFS_IOLOCK_SHARED);
>  	if (ret)
>  		return ret;
>  	ret = iomap_dio_rw(iocb, to, &xfs_read_iomap_ops, NULL, 0, 0);
> @@ -244,7 +243,7 @@ xfs_file_dax_read(
>  	if (!iov_iter_count(to))
>  		return 0; /* skip atime */
>  
> -	ret = xfs_ilock_iocb(iocb, XFS_IOLOCK_SHARED);
> +	ret = xfs_ilock_xfs_inode(ip, iocb->ki_flags, XFS_IOLOCK_SHARED);
>  	if (ret)
>  		return ret;
>  	ret = dax_iomap_rw(iocb, to, &xfs_read_iomap_ops);
> @@ -264,7 +263,7 @@ xfs_file_buffered_read(
>  
>  	trace_xfs_file_buffered_read(iocb, to);
>  
> -	ret = xfs_ilock_iocb(iocb, XFS_IOLOCK_SHARED);
> +	ret = xfs_ilock_xfs_inode(ip, iocb->ki_flags, XFS_IOLOCK_SHARED);
>  	if (ret)
>  		return ret;
>  	ret = generic_file_read_iter(iocb, to);
> @@ -343,7 +342,7 @@ xfs_file_write_checks(
>  	if (*iolock == XFS_IOLOCK_SHARED && !IS_NOSEC(inode)) {
>  		xfs_iunlock(ip, *iolock);
>  		*iolock = XFS_IOLOCK_EXCL;
> -		error = xfs_ilock_iocb(iocb, *iolock);
> +		error = xfs_ilock_xfs_inode(ip, iocb->ki_flags, *iolock);
>  		if (error) {
>  			*iolock = 0;
>  			return error;
> @@ -516,7 +515,7 @@ xfs_file_dio_write_aligned(
>  	int			iolock = XFS_IOLOCK_SHARED;
>  	ssize_t			ret;
>  
> -	ret = xfs_ilock_iocb(iocb, iolock);
> +	ret = xfs_ilock_xfs_inode(ip, iocb->ki_flags, iolock);
>  	if (ret)
>  		return ret;
>  	ret = xfs_file_write_checks(iocb, from, &iolock);
> @@ -583,7 +582,7 @@ xfs_file_dio_write_unaligned(
>  		flags = IOMAP_DIO_FORCE_WAIT;
>  	}
>  
> -	ret = xfs_ilock_iocb(iocb, iolock);
> +	ret = xfs_ilock_xfs_inode(ip, iocb->ki_flags, iolock);
>  	if (ret)
>  		return ret;
>  
> @@ -659,7 +658,7 @@ xfs_file_dax_write(
>  	ssize_t			ret, error = 0;
>  	loff_t			pos;
>  
> -	ret = xfs_ilock_iocb(iocb, iolock);
> +	ret = xfs_ilock_xfs_inode(ip, iocb->ki_flags, iolock);
>  	if (ret)
>  		return ret;
>  	ret = xfs_file_write_checks(iocb, from, &iolock);
> @@ -702,12 +701,11 @@ xfs_file_buffered_write(
>  	bool			cleared_space = false;
>  	int			iolock;
>  
> -	if (iocb->ki_flags & IOCB_NOWAIT)
> -		return -EOPNOTSUPP;
> -
>  write_retry:
>  	iolock = XFS_IOLOCK_EXCL;
> -	xfs_ilock(ip, iolock);
> +	ret = xfs_ilock_xfs_inode(ip, iocb->ki_flags, iolock);
> +	if (ret)
> +		return ret;
>  
>  	ret = xfs_file_write_checks(iocb, from, &iolock);
>  	if (ret)
> -- 
> 2.30.2
> 

  parent reply	other threads:[~2022-05-22 15:35 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 18:36 [RFC PATCH v4 00/17] io-uring/xfs: support async buffered writes Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 01/17] mm: Move starting of background writeback into the main balancing loop Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 02/17] mm: Move updates of dirty_exceeded into one place Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 03/17] mm: Prepare balance_dirty_pages() for async buffered writes Stefan Roesch
2022-05-22  7:17   ` Christoph Hellwig
2022-05-25 21:30     ` Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 04/17] mm: Add balance_dirty_pages_ratelimited_flags() function Stefan Roesch
2022-05-23 10:40   ` Jan Kara
2022-05-20 18:36 ` [RFC PATCH v4 05/17] iomap: Add gfp parameter to iomap_page_create() Stefan Roesch
2022-05-22  7:21   ` Christoph Hellwig
2022-05-25 21:29     ` Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 06/17] iomap: Add async buffered write support Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 07/17] iomap: Use balance_dirty_pages_ratelimited_flags in iomap_write_iter Stefan Roesch
2022-05-22  7:19   ` Christoph Hellwig
2022-05-25 21:32     ` Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 08/17] fs: Add check for async buffered writes to generic_write_checks Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 09/17] fs: Split off remove_needs_file_privs() __remove_file_privs() Stefan Roesch
2022-05-22  7:32   ` Christoph Hellwig
2022-05-25 21:34     ` Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 10/17] fs: Split off file_needs_update_time and __file_update_time Stefan Roesch
2022-05-22  7:29   ` Christoph Hellwig
2022-05-25 22:32     ` Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 11/17] fs: Add async write file modification handling Stefan Roesch
2022-05-22  7:24   ` Christoph Hellwig
2022-05-25 21:39     ` Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 12/17] fs: Optimization for concurrent file time updates Stefan Roesch
2022-05-23 10:51   ` Jan Kara
2022-05-25 21:46     ` Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 13/17] io_uring: Add support for async buffered writes Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 14/17] io_uring: Add tracepoint for short writes Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 15/17] xfs: Add iomap async buffered write support Stefan Roesch
2022-05-22  7:33   ` Christoph Hellwig
2022-05-25 21:40     ` Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 16/17] xfs: Add " Stefan Roesch
2022-05-22  7:34   ` Christoph Hellwig
2022-05-25 21:41     ` Stefan Roesch
2022-05-22 15:35   ` Darrick J. Wong [this message]
2022-05-25 21:44     ` Stefan Roesch
2022-05-20 18:36 ` [RFC PATCH v4 17/17] xfs: Enable " Stefan Roesch

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=YopYP9vI7E7LbjiD@magnolia \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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