public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Vitaliy Filippov <[email protected]>,
	"[email protected]" <[email protected]>,
	Jens Axboe <[email protected]>
Subject: Re: write / fsync ordering
Date: Tue, 28 Jan 2020 13:46:07 +0300	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <op.0e3l6cmc0ncgu9@localhost>

On 1/28/2020 1:31 PM, Vitaliy Filippov wrote:
> Hi everyone,
> 
> Can someone point out if io_uring may reorder write and fsync requests?
> 
> If I submit a write request and an fsync request at the same time, does
> that mean that fsync will sync that write request, or does it only sync
> completed requests?

Yes, it can reorder them. So, there are 2 ways:
- wait for the completion
- order the requests within io_uring

I'd recommend the ordering option by using IOSQE_IO_LINK, which
guarantees sequential execution of linked requests. There is also
IOSQE_IO_DRAIN, but it's rather inefficient.

-- 
Pavel Begunkov

  reply	other threads:[~2020-01-28 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28 10:31 write / fsync ordering Vitaliy Filippov
2020-01-28 10:46 ` Pavel Begunkov [this message]
2020-01-28 10:55   ` Vitaliy Filippov

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] \
    /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