From: Youling Tang <youling.tang@linux.dev>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Youling Tang <tangyouling@kylinos.cn>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] fs/direct-io: Remove linux/prefetch.h include
Date: Wed, 24 Jul 2024 15:33:38 +0800 [thread overview]
Message-ID: <cfce353d-e5b0-47be-9a02-be4558d4dc33@linux.dev> (raw)
In-Reply-To: <20240603111844.l4g2yk5q6z23cz3n@quack3>
Hi,
On 03/06/2024 19:18, Jan Kara wrote:
> On Mon 03-06-24 09:48:34, Youling Tang wrote:
>> From: Youling Tang <tangyouling@kylinos.cn>
>>
>> After commit c22198e78d52 ("direct-io: remove random prefetches"), Nothing
>> in this file needs anything from `linux/prefetch.h`.
>>
>> Signed-off-by: Youling Tang <tangyouling@kylinos.cn>
Sorry to bother you, but do we still need this patch?
Thanks,
Youling.
> Looks good. Feel free to add:
>
> Reviewed-by: Jan Kara <jack@suse.cz>
>
> Honza
>
>> ---
>> fs/direct-io.c | 6 ------
>> 1 file changed, 6 deletions(-)
>>
>> diff --git a/fs/direct-io.c b/fs/direct-io.c
>> index b0aafe640fa4..bbd05f1a2145 100644
>> --- a/fs/direct-io.c
>> +++ b/fs/direct-io.c
>> @@ -37,7 +37,6 @@
>> #include <linux/rwsem.h>
>> #include <linux/uio.h>
>> #include <linux/atomic.h>
>> -#include <linux/prefetch.h>
>>
>> #include "internal.h"
>>
>> @@ -1121,11 +1120,6 @@ ssize_t __blockdev_direct_IO(struct kiocb *iocb, struct inode *inode,
>> struct blk_plug plug;
>> unsigned long align = offset | iov_iter_alignment(iter);
>>
>> - /*
>> - * Avoid references to bdev if not absolutely needed to give
>> - * the early prefetch in the caller enough time.
>> - */
>> -
>> /* watch out for a 0 len io from a tricksy fs */
>> if (iov_iter_rw(iter) == READ && !count)
>> return 0;
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2024-07-24 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 1:48 [PATCH] fs/direct-io: Remove linux/prefetch.h include Youling Tang
2024-06-03 11:18 ` Jan Kara
2024-07-24 7:33 ` Youling Tang [this message]
2024-07-26 7:16 ` Christian Brauner
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=cfce353d-e5b0-47be-9a02-be4558d4dc33@linux.dev \
--to=youling.tang@linux.dev \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tangyouling@kylinos.cn \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).