From: vincentfu@gmail.com
To: axboe@kernel.dk, fio@vger.kernel.org
Cc: Vincent Fu <vincent.fu@wdc.com>
Subject: [PATCH v2 0/4] cross-job overlap patches
Date: Wed, 17 Oct 2018 10:52:21 -0400 [thread overview]
Message-ID: <20181017145225.14546-1-vincentfu@gmail.com> (raw)
From: Vincent Fu <vincent.fu@wdc.com>
Jens, this series of patches allocates io_u's and io_u_all members from
shared memory when serialize_overlap=1 and io_submit_mode=offload so
that processes can now be used. Also included are the locking comments
you requested and some other cleanups. Please let me know what comments
you have.
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 | 19 +++++++++++++++----
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, 74 insertions(+), 29 deletions(-)
--
2.17.1
next reply other threads:[~2018-10-17 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 14:52 vincentfu [this message]
2018-10-17 14:52 ` [PATCH v2 1/4] fio: add function to check for serialize_overlap with offload submission vincentfu
2018-10-17 15:33 ` Sébastien Boisvert
2018-10-17 14:52 ` [PATCH v2 2/4] fio: enable cross-thread overlap checking with processes vincentfu
2018-10-17 15:32 ` Jens Axboe
2018-10-17 14:52 ` [PATCH v2 3/4] fio: document locking for overlap checking in offload mode vincentfu
2018-10-17 14:52 ` [PATCH v2 4/4] docs: serialize_overlap=1 with io_submit_mode=offload no longer requires threads vincentfu
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=20181017145225.14546-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