linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH liburing 0/2] Memory synchronization improvements
Date: Mon,  1 Jul 2019 14:42:30 -0700	[thread overview]
Message-ID: <20190701214232.29338-1-bvanassche@acm.org> (raw)

Hi Jens,

The two patches in this series reduce the number of memory barrier calls from
liburing and also fix a few memory synchronization bugs. Please consider these
patches for the official liburing git repository.

Thanks,

Bart.

Bart Van Assche (2):
  __io_uring_get_cqe(): Use io_uring_for_each_cqe()
  Fix the use of memory barriers

 man/io_uring_setup.2  |  6 ++-
 src/barrier.h         | 87 +++++++++++++++++++++++++++++++++++++++++--
 src/liburing.h        | 15 +++-----
 src/queue.c           | 48 ++++++------------------
 test/io_uring_enter.c |  8 ++--
 5 files changed, 110 insertions(+), 54 deletions(-)

-- 
2.22.0.410.gd8fdbe21b5-goog


             reply	other threads:[~2019-07-01 21:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 21:42 Bart Van Assche [this message]
2019-07-01 21:42 ` [PATCH liburing 1/2] __io_uring_get_cqe(): Use io_uring_for_each_cqe() Bart Van Assche
2019-07-01 21:42 ` [PATCH liburing 2/2] Fix the use of memory barriers Bart Van Assche
2019-07-02  9:07   ` Roman Penyaev
2019-07-02 16:17     ` Bart Van Assche
2019-07-02 18:40       ` Roman Penyaev
2019-07-02 20:31         ` Bart Van Assche
2019-07-03  9:49           ` Roman Penyaev
2019-07-03 20:49             ` Bart Van Assche
2019-07-02 16:18 ` [PATCH liburing 0/2] Memory synchronization improvements Jens Axboe

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=20190701214232.29338-1-bvanassche@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    /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).