From: Yin Fengwei <[email protected]>
To: Jens Axboe <[email protected]>, kernel test robot <[email protected]>
Cc: LKML <[email protected]>, <[email protected]>,
<[email protected]>, <[email protected]>
Subject: Re: [LKP] Re: [io_uring] 584b0180f0: phoronix-test-suite.fio.SequentialWrite.IO_uring.Yes.Yes.1MB.DefaultTestDirectory.mb_s -10.2% regression
Date: Mon, 18 Jul 2022 11:30:34 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Hi Jens,
On 7/15/2022 11:58 PM, Jens Axboe wrote:
> In terms of making this more obvious, does the below also fix it for
> you?
The regression is still there after applied the change you posted.
Your change can't be applied to v5.18 (the latest commit on master branch).
I changed it a little bit to be applied:
diff --git a/fs/io_uring.c b/fs/io_uring.c
index e0823f58f7959..0bf7f3d18d46e 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -3762,9 +3762,6 @@ static int io_rw_init_file(struct io_kiocb *req, fmode_t mode)
if (unlikely(!file || !(file->f_mode & mode)))
return -EBADF;
- if (!io_req_ffs_set(req))
- req->flags |= io_file_get_flags(file) << REQ_F_SUPPORT_NOWAIT_BIT;
-
kiocb->ki_flags = iocb_flags(file);
ret = kiocb_set_rw_flags(kiocb, req->rw.flags);
if (unlikely(ret))
@@ -7114,8 +7111,13 @@ static bool io_assign_file(struct io_kiocb *req, unsigned int issue_flags)
req->file = io_file_get_fixed(req, req->fd, issue_flags);
else
req->file = io_file_get_normal(req, req->fd);
- if (req->file)
+ if (req->file) {
+ if (!io_req_ffs_set(req))
+ req->flags |= io_file_get_flags(req->file) <<
+ REQ_F_SUPPORT_NOWAIT_BIT;
+
return true;
+ }
req_set_fail(req);
req->result = -EBADF;
Regards
Yin, Fengwei
next prev parent reply other threads:[~2022-07-18 3:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220527092432.GE11731@xsang-OptiPlex-9020>
2022-05-27 13:50 ` [io_uring] 584b0180f0: phoronix-test-suite.fio.SequentialWrite.IO_uring.Yes.Yes.1MB.DefaultTestDirectory.mb_s -10.2% regression Jens Axboe
2022-06-08 8:00 ` Oliver Sang
2022-06-14 1:54 ` [LKP] " Yin Fengwei
2022-07-12 8:06 ` Yin Fengwei
2022-07-15 15:58 ` Jens Axboe
2022-07-18 0:58 ` Yin Fengwei
2022-07-18 1:14 ` Jens Axboe
2022-07-18 3:30 ` Yin Fengwei [this message]
2022-07-18 16:27 ` Jens Axboe
2022-07-19 0:27 ` Yin Fengwei
2022-07-19 2:16 ` Yin Fengwei
2022-07-19 2:29 ` Jens Axboe
2022-07-19 8:58 ` Yin Fengwei
2022-07-20 17:24 ` Jens Axboe
2022-07-20 18:13 ` Jens Axboe
2022-07-20 23:25 ` Yin Fengwei
2022-07-21 2:59 ` Yin Fengwei
2022-07-21 3:08 ` Yin Fengwei
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 \
[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