From: Jens Axboe <[email protected]>
To: Daniel Black <[email protected]>,
Salvatore Bonaccorso <[email protected]>
Cc: Pavel Begunkov <[email protected]>,
[email protected], [email protected]
Subject: Re: uring regression - lost write request
Date: Wed, 10 Nov 2021 11:01:45 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/9/21 4:24 PM, Jens Axboe wrote:
> On 11/9/21 3:58 PM, Daniel Black wrote:
>>> On Sat, Oct 30, 2021 at 6:30 PM Salvatore Bonaccorso <[email protected]> wrote:
>>>> Were you able to pinpoint the issue?
>>
>> While I have been unable to reproduce this on a single cpu, Marko can
>> repeat a stall on a dual Broadwell chipset on kernels:
>>
>> * 5.15.1 - https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15.1
>> * 5.14.16 - https://packages.debian.org/sid/linux-image-5.14.0-4-amd64
>>
>> Detailed observations:
>> https://jira.mariadb.org/browse/MDEV-26674
>>
>> The previous script has been adapted to use MariaDB-10.6 package and
>> sysbench to demonstrate a workload, I've changed Marko's script to
>> work with the distro packages and use innodb_use_native_aio=1.
>>
>> MariaDB packages:
>>
>> https://mariadb.org/download/?t=repo-config
>> (needs a distro that has liburing userspace libraries as standard support)
>>
>> Script:
>>
>> https://jira.mariadb.org/secure/attachment/60358/Mariabench-MDEV-26674-io_uring-1
>>
>> The state is achieved either when the sysbench prepare stalls, or the
>> tps printed at 5 second intervals falls to 0.
>
> Thanks, this is most useful! I'll take a look at this.
Would it be possible to turn this into a full reproducer script?
Something that someone that knows nothing about mysqld/mariadb can just
run and have it reproduce. If I install the 10.6 packages from above,
then it doesn't seem to use io_uring or be linked against liburing.
The script also seems to assume that various things are setup
appropriately, like SRCTREE, MDIR, etc.
--
Jens Axboe
next prev parent reply other threads:[~2021-11-10 18:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABVffENnJ8JkP7EtuUTqi+VkJDBFU37w1UXe4Q3cB7-ixxh0VA@mail.gmail.com>
2021-10-22 9:10 ` uring regression - lost write request Pavel Begunkov
2021-10-25 9:57 ` Pavel Begunkov
2021-10-25 11:09 ` Daniel Black
2021-10-25 11:25 ` Pavel Begunkov
2021-10-30 7:30 ` Salvatore Bonaccorso
2021-11-01 7:28 ` Daniel Black
2021-11-09 22:58 ` Daniel Black
2021-11-09 23:24 ` Jens Axboe
2021-11-10 18:01 ` Jens Axboe [this message]
2021-11-11 6:52 ` Daniel Black
2021-11-11 14:30 ` Jens Axboe
2021-11-11 14:58 ` Jens Axboe
2021-11-11 15:29 ` Jens Axboe
2021-11-11 16:19 ` Jens Axboe
2021-11-11 16:55 ` Jens Axboe
2021-11-11 17:28 ` Jens Axboe
2021-11-11 23:44 ` Jens Axboe
2021-11-12 6:25 ` Daniel Black
2021-11-12 19:19 ` Salvatore Bonaccorso
2021-11-14 20:33 ` Daniel Black
2021-11-14 20:55 ` Jens Axboe
2021-11-14 21:02 ` Salvatore Bonaccorso
2021-11-14 21:03 ` Jens Axboe
2021-11-24 3:27 ` Daniel Black
2021-11-24 15:28 ` Jens Axboe
2021-11-24 16:10 ` Jens Axboe
2021-11-24 16:18 ` Greg Kroah-Hartman
2021-11-24 16:22 ` Jens Axboe
2021-11-24 22:52 ` Stefan Metzmacher
2021-11-25 0:58 ` Jens Axboe
2021-11-25 16:35 ` Stefan Metzmacher
2021-11-25 17:11 ` Jens Axboe
2022-02-09 23:01 ` Stefan Metzmacher
2022-02-10 0:10 ` Daniel Black
2021-11-24 22:57 ` Daniel Black
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] \
/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