From: SeongJae Park <sjpark@amazon.com>
To: <sjpark@amazon.com>
Cc: <axboe@kernel.dk>, <konrad.wilk@oracle.com>,
<linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<pdurrant@amazon.com>, <roger.pau@citrix.com>,
<sj38.park@gmail.com>, <xen-devel@lists.xenproject.org>
Subject: [PATCH v4 0/2] xenbus/backend: Add a memory pressure handler callback
Date: Mon, 9 Dec 2019 20:43:03 +0100 [thread overview]
Message-ID: <20191209194305.20828-1-sjpark@amazon.com> (raw)
Granting pages consumes backend system memory. In systems configured
with insufficient spare memory for those pages, it can cause a memory
pressure situation. However, finding the optimal amount of the spare
memory is challenging for large systems having dynamic resource
utilization patterns. Also, such a static configuration might lacks a
flexibility.
To mitigate such problems, this patchset adds a memory reclaim callback
to 'xenbus_driver' (patch 1) and use it to mitigate the problem in
'xen-blkback' (patch 2).
Base Version
------------
This patch is based on v5.4. A complete tree is also available at my
public git repo:
https://github.com/sjp38/linux/tree/blkback_squeezing_v4
Patch History
-------------
Changes from v3 (https://lore.kernel.org/xen-devel/20191209085839.21215-1-sjpark@amazon.com/)
- Add general callback in xen_driver and use it (suggested by Juergen
Gross)
Changes from v2 (https://lore.kernel.org/linux-block/af195033-23d5-38ed-b73b-f6e2e3b34541@amazon.com)
- Rename the module parameter and variables for brevity (aggressive
shrinking -> squeezing)
Changes from v1 (https://lore.kernel.org/xen-devel/20191204113419.2298-1-sjpark@amazon.com/)
- Adjust the description to not use the term, `arbitrarily` (suggested
by Paul Durrant)
- Specify time unit of the duration in the parameter description,
(suggested by Maximilian Heyne)
- Change default aggressive shrinking duration from 1ms to 10ms
- Merge two patches into one single patch
SeongJae Park (1):
xen/blkback: Squeeze page pools if a memory pressure is detected
drivers/block/xen-blkback/blkback.c | 35 +++++++++++++++++++++++++++--
1 file changed, 33 insertions(+), 2 deletions(-)
SeongJae Park (2):
xenbus/backend: Add memory pressure handler callback
xen/blkback: Squeeze page pools if a memory pressure is detected
drivers/block/xen-blkback/blkback.c | 23 +++++++++++++++--
drivers/block/xen-blkback/common.h | 1 +
drivers/block/xen-blkback/xenbus.c | 3 ++-
drivers/xen/xenbus/xenbus_probe_backend.c | 31 +++++++++++++++++++++++
include/xen/xenbus.h | 1 +
5 files changed, 56 insertions(+), 3 deletions(-)
--
2.17.1
next reply other threads:[~2019-12-09 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 19:43 SeongJae Park [this message]
2019-12-09 19:43 ` [PATCH v4 1/2] xenbus/backend: Add " SeongJae Park
2019-12-10 6:11 ` Jürgen Groß
2019-12-10 6:19 ` SeongJae Park
2019-12-10 6:23 ` Jürgen Groß
2019-12-10 6:29 ` SeongJae Park
2019-12-09 19:43 ` [PATCH v4 2/2] xen/blkback: Squeeze page pools if a memory pressure is detected SeongJae Park
2019-12-10 6:24 ` Jürgen Groß
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=20191209194305.20828-1-sjpark@amazon.com \
--to=sjpark@amazon.com \
--cc=axboe@kernel.dk \
--cc=konrad.wilk@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pdurrant@amazon.com \
--cc=roger.pau@citrix.com \
--cc=sj38.park@gmail.com \
--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
all inboxes | Powered by JetHome®