From: vincentfu@gmail.com
To: axboe@kernel.dk, fio@vger.kernel.org, vincentfu@gmail.com
Cc: Vincent Fu <vincent.fu@wdc.com>
Subject: [PATCH v3 0/4] cross-job overlap patches
Date: Wed, 17 Oct 2018 12:03:21 -0400 [thread overview]
Message-ID: <20181017160325.16866-1-vincentfu@gmail.com> (raw)
From: Vincent Fu <vincent.fu@wdc.com>
Jens, I have updated the patch series in response to the latest
comments. Specifically, I have
- removed the unneeded parentheses in PATCH 1/4
- removed the unneeded memset in PATCH 2/4
Please let me know if you see any other issues.
Vincent
Vincent Fu (4):
fio: add function to check for serialize_overlap with offload
submission
fio: enable cross-thread overlap checking with processes
fio: document locking for overlap checking in offload mode
docs: serialize_overlap=1 with io_submit_mode=offload no longer
requires threads
HOWTO | 2 +-
backend.c | 21 +++++++++++++--------
fio.1 | 2 +-
fio.h | 5 +++++
io_u_queue.c | 17 +++++++++++++----
io_u_queue.h | 4 ++--
ioengines.c | 9 ++++++++-
lib/memalign.c | 16 ++++++++++++----
lib/memalign.h | 5 +++--
rate-submit.c | 8 ++++++++
t/dedupe.c | 12 ++++++------
11 files changed, 72 insertions(+), 29 deletions(-)
--
2.17.1
next reply other threads:[~2018-10-17 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 16:03 vincentfu [this message]
2018-10-17 16:03 ` [PATCH v3 1/4] fio: add function to check for serialize_overlap with offload submission vincentfu
2018-10-17 16:03 ` [PATCH v3 2/4] fio: enable cross-thread overlap checking with processes vincentfu
2018-10-17 16:25 ` Sébastien Boisvert
2018-10-17 16:26 ` Jens Axboe
2018-10-17 16:03 ` [PATCH v3 3/4] fio: document locking for overlap checking in offload mode vincentfu
2018-10-17 16:03 ` [PATCH v3 4/4] docs: serialize_overlap=1 with io_submit_mode=offload no longer requires threads vincentfu
2018-10-19 17:10 ` [PATCH v3 0/4] cross-job overlap patches 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=20181017160325.16866-1-vincentfu@gmail.com \
--to=vincentfu@gmail.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=vincent.fu@wdc.com \
/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