From: SeongJae Park <sjpark@amazon.com>
To: <konrad.wilk@oracle.com>, <roger.pau@citrix.com>, <jgross@suse.com>
Cc: SeongJae Park <sjpark@amazon.de>, <axboe@kernel.dk>,
<aliguori@amazon.com>, <amit@kernel.org>, <mheyne@amazon.de>,
<pdurrant@amazon.co.uk>, <linux-block@vger.kernel.org>,
<xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v4 0/3] xen-blk(back|front): Let users disable persistent grants
Date: Wed, 23 Sep 2020 08:18:38 +0200 [thread overview]
Message-ID: <20200923061841.20531-1-sjpark@amazon.com> (raw)
From: SeongJae Park <sjpark@amazon.de>
Persistent grants feature provides high scalability. On some small
systems, however, it could incur data copy overheads[1] and thus it is
required to be disabled. But, there is no option to disable it. For
the reason, this commit adds module parameters for disabling of the
feature.
[1] https://wiki.xen.org/wiki/Xen_4.3_Block_Protocol_Scalability
Baseline and Complete Git Trees
===============================
The patches are based on the v5.9-rc6. You can also clone the complete
git tree:
$ git clone git://github.com/sjp38/linux -b pgrants_disable_v4
The web is also available:
https://github.com/sjp38/linux/tree/pgrants_disable_v4
Patch History
=============
Changes from v3
(https://lore.kernel.org/xen-devel/20200922141549.26154-2-sjpark@amazon.com/)
- Remove unnecessary ternary operation (Jürgen Groß)
- Add 'Reviewed-by: Juergen Gross <jgross@suse.com>' and
'Acked-by: Roger Pau Monné <roger.pau@citrix.com>'
Changes from v2
(https://lore.kernel.org/linux-block/20200922105209.5284-1-sjpark@amazon.com/)
- Avoid a race condition (Roger Pau Monné)
Because the option value is written twice, there could be a race if the
user change the value meanwhile. This version fixes the problem by
reading the value once when each (front|back)end is created.
Changes from v1
(https://lore.kernel.org/linux-block/20200922070125.27251-1-sjpark@amazon.com/)
- use 'bool' parameter type (Jürgen Groß)
- Let blkfront can also disable the feature from its side
(Roger Pau Monné)
- Avoid unnecessary xenbus_printf (Roger Pau Monné)
- Update frontend parameter doc
SeongJae Park (3):
xen-blkback: add a parameter for disabling of persistent grants
xen-blkfront: add a parameter for disabling of persistent grants
xen-blkfront: Apply changed parameter name to the document
.../ABI/testing/sysfs-driver-xen-blkback | 9 ++++++++
.../ABI/testing/sysfs-driver-xen-blkfront | 11 +++++++++-
drivers/block/xen-blkback/xenbus.c | 22 ++++++++++++++-----
drivers/block/xen-blkfront.c | 20 ++++++++++++-----
4 files changed, 50 insertions(+), 12 deletions(-)
--
2.17.1
next reply other threads:[~2020-09-23 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 6:18 SeongJae Park [this message]
2020-09-23 6:18 ` [PATCH v4 1/3] xen-blkback: add a parameter for disabling of persistent grants SeongJae Park
2020-09-23 6:18 ` [PATCH v4 2/3] xen-blkfront: " SeongJae Park
2020-09-23 6:18 ` [PATCH v4 3/3] xen-blkfront: Apply changed parameter name to the document SeongJae Park
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=20200923061841.20531-1-sjpark@amazon.com \
--to=sjpark@amazon.com \
--cc=aliguori@amazon.com \
--cc=amit@kernel.org \
--cc=axboe@kernel.dk \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mheyne@amazon.de \
--cc=pdurrant@amazon.co.uk \
--cc=roger.pau@citrix.com \
--cc=sjpark@amazon.de \
--cc=xen-devel@lists.xenproject.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).