From: Jens Axboe <[email protected]>
To: Dmitry Shulyak <[email protected]>
Cc: [email protected]
Subject: Re: Very low write throughput on file opened with O_SYNC/O_DSYNC
Date: Tue, 18 Aug 2020 09:42:17 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAF-ewDqANgn-F=9bQiXZtLyPXOs2Dwi-CHS=80hXpiZYGrJjgg@mail.gmail.com>
On 8/18/20 9:09 AM, Dmitry Shulyak wrote:
> it worked, but there are some issues.
> with o_dsync and even moderate submission rate threads are stuck in
> some cpu task (99.9% cpu consumption), and make very slow progress.
> have you expected it? it must be something specific to uring, i can't
> reproduce this condition by writing from 2048 threads.
Do you have a reproducer I can run? Curious what that CPU spin is,
that obviously shouldn't happen.
--
Jens Axboe
next prev parent reply other threads:[~2020-08-18 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 11:46 Very low write throughput on file opened with O_SYNC/O_DSYNC Dmitry Shulyak
2020-08-17 11:58 ` Dmitry Shulyak
2020-08-17 14:29 ` Jens Axboe
2020-08-17 15:49 ` Dmitry Shulyak
2020-08-17 16:17 ` Jens Axboe
2020-08-18 16:09 ` Dmitry Shulyak
2020-08-18 16:42 ` Jens Axboe [this message]
2020-08-19 7:55 ` Dmitry Shulyak
2020-08-21 13:43 ` Dmitry Shulyak
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] \
/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