public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Matthew Wilcox <willy@infradead.org>, Liu Wei <liuwei09@cestc.cn>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	Goldwyn Rodrigues <rgoldwyn@suse.com>,
	Christoph Hellwig <hch@lst.de>, Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] mm/filemap: invalidating pages is still necessary when io with IOCB_NOWAIT
Date: Thu, 23 May 2024 15:16:38 -0600	[thread overview]
Message-ID: <024b9a30-ad3b-4063-b5c8-e6c948ad6b2e@kernel.dk> (raw)
In-Reply-To: <Zk-wa_GvvrxpX9kn@casper.infradead.org>

On 5/23/24 3:08 PM, Matthew Wilcox wrote:
> On Mon, May 13, 2024 at 09:23:39PM +0800, Liu Wei wrote:
>> After commit (6be96d3ad3 fs: return if direct I/O will trigger writeback),
> 
> If you're reporting problems with a particular commit, it's good form
> to cc the people who actually wrote that commit.

Yeah indeed...

>> when we issuing AIO with direct I/O and IOCB_NOWAIT on a block device, the
>> process context will not be blocked.
>>
>> However, if the device already has page cache in memory, EAGAIN will be
>> returned. And even when trying to reissue the AIO with direct I/O and
>> IOCB_NOWAIT again, we consistently receive EAGAIN.

-EAGAIN doesn't mean "just try again and it'll work".

>> Maybe a better way to deal with it: filemap_fdatawrite_range dirty pages
>> with WB_SYNC_NONE flag, and invalidate_mapping_pages unmapped pages at
>> the same time.
>>
>> Signed-off-by: Liu Wei <liuwei09@cestc.cn>
>> ---
>>  mm/filemap.c | 9 ++++++++-
>>  1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/mm/filemap.c b/mm/filemap.c
>> index 30de18c4fd28..1852a00caf31 100644
>> --- a/mm/filemap.c
>> +++ b/mm/filemap.c
>> @@ -2697,8 +2697,15 @@ int kiocb_invalidate_pages(struct kiocb *iocb, size_t count)
>>  
>>  	if (iocb->ki_flags & IOCB_NOWAIT) {
>>  		/* we could block if there are any pages in the range */
>> -		if (filemap_range_has_page(mapping, pos, end))
>> +		if (filemap_range_has_page(mapping, pos, end)) {
>> +			if (mapping_needs_writeback(mapping)) {
>> +				__filemap_fdatawrite_range(mapping,
>> +						pos, end, WB_SYNC_NONE);
>> +			}

I don't think WB_SYNC_NONE tells it not to block, it just says not to
wait for it... So this won't work as-is.

>> +			invalidate_mapping_pages(mapping,
>> +					pos >> PAGE_SHIFT, end >> PAGE_SHIFT);
>>  			return -EAGAIN;
>> +		}
>>  	} else {
>>  		ret = filemap_write_and_wait_range(mapping, pos, end);
>>  		if (ret)
>> -- 
>> 2.42.1
>>
>>
>>

-- 
Jens Axboe


  reply	other threads:[~2024-05-23 21:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 13:23 [PATCH] mm/filemap: invalidating pages is still necessary when io with IOCB_NOWAIT Liu Wei
2024-05-23 20:08 ` Andrew Morton
2024-05-23 21:11   ` Matthew Wilcox
2024-05-23 21:17     ` Jens Axboe
2024-05-23 21:08 ` Matthew Wilcox
2024-05-23 21:16   ` Jens Axboe [this message]
2024-05-27 10:09     ` Liu Wei
2024-05-27 15:36       ` Jens Axboe
2024-05-30  2:33         ` Liu Wei

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=024b9a30-ad3b-4063-b5c8-e6c948ad6b2e@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuwei09@cestc.cn \
    --cc=rgoldwyn@suse.com \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox