From: "Wunderlich, Mark" <mark.wunderlich@intel.com>
To: Sagi Grimberg <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Jens Axboe <axboe@kernel.dk>
Subject: RE: Sighting: Kernel fault with large write (512k) and io_uring
Date: Mon, 23 Mar 2020 23:16:06 +0000 [thread overview]
Message-ID: <MW3PR11MB4684FD29002D6D1FE29A4A0FE5F00@MW3PR11MB4684.namprd11.prod.outlook.com> (raw)
In-Reply-To: <092f6922-ab29-c2bc-04b8-0d0c95c14ad6@grimberg.me>
i> OK, this is a needed fix then.
Yes, so far this removed the kernel fault seen for large write (512k) + queue depth 32 + batch size 8.
>Yes, this is with nvme-5.7 tree right? which is currently based of
>5.6.0-rc4 correct?
No, was not yet able to get branch 5.7 to build with our driver. For now am running on branch nvme-5.6-rc6, the other branch mentioned by Jens to try. This appears to be based on 5.6.0-rc3 I believe. Will re-test on 5.7 once I can get it ready.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-03-23 23:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 23:37 Sighting: Kernel fault with large write (512k) and io_uring Wunderlich, Mark
2020-03-19 1:12 ` Sagi Grimberg
2020-03-19 2:33 ` Jens Axboe
2020-03-23 21:07 ` Wunderlich, Mark
2020-03-23 21:11 ` Sagi Grimberg
2020-03-23 21:18 ` Sagi Grimberg
2020-03-23 22:04 ` Wunderlich, Mark
2020-03-23 22:09 ` Sagi Grimberg
2020-03-23 23:16 ` Wunderlich, Mark [this message]
2020-03-23 23:29 ` Sagi Grimberg
2020-03-23 23:45 ` Wunderlich, Mark
2020-03-23 23:48 ` Sagi Grimberg
2020-03-24 0:34 ` Wunderlich, Mark
2020-03-24 1:29 ` Sagi Grimberg
2020-03-24 16:31 ` Wunderlich, Mark
2020-03-24 19:13 ` Sagi Grimberg
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=MW3PR11MB4684FD29002D6D1FE29A4A0FE5F00@MW3PR11MB4684.namprd11.prod.outlook.com \
--to=mark.wunderlich@intel.com \
--cc=axboe@kernel.dk \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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).