From: SeongJae Park <sj38.park@gmail.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: jgross@suse.com, axboe@kernel.dk, konrad.wilk@oracle.com,
"SeongJae Park" <sjpark@amazon.de>,
pdurrant@amazon.com, sjpark@amazon.com,
xen-devel@lists.xenproject.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH v6 1/3] xenbus/backend: Add memory pressure handler callback
Date: Wed, 11 Dec 2019 13:20:11 +0100 [thread overview]
Message-ID: <20191211122011.16231-1-sj38.park@gmail.com> (raw)
In-Reply-To: <20191211114651.GN980@Air-de-Roger> (raw)
On Wed, 11 Dec 2019 12:46:51 +0100 "Roger Pau Monné" <roger.pau@citrix.com> wrote:
> > 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
> ^ s/the//
> > memory is challenging for large systems having dynamic resource
> > utilization patterns. Also, such a static configuration might lack
> > flexibility.
> >
> > To mitigate such problems, this commit adds a memory reclaim callback to
> > 'xenbus_driver'. If a memory pressure is detected, 'xenbus' requests
> ^ s/a//
> > every backend driver to volunarily release its memory.
> >
> > Note that it would be able to improve the callback facility for more
> ^ possible
> > sophisticated handlings of general pressures. For example, it would be
> ^ handling of resource starvation.
> > possible to monitor the memory consumption of each device and issue the
> > release requests to only devices which causing the pressure. Also, the
> > callback could be extended to handle not only memory, but general
> > resources. Nevertheless, this version of the implementation defers such
> > sophisticated goals as a future work.
> >
> > Reviewed-by: Juergen Gross <jgross@suse.com>
> > Signed-off-by: SeongJae Park <sjpark@amazon.de>
> > ---
> > drivers/xen/xenbus/xenbus_probe_backend.c | 32 +++++++++++++++++++++++
> > include/xen/xenbus.h | 1 +
> > 2 files changed, 33 insertions(+)
> >
> > diff --git a/drivers/xen/xenbus/xenbus_probe_backend.c b/drivers/xen/xenbus/xenbus_probe_backend.c
> > index b0bed4faf44c..aedbe2198de5 100644
> > --- a/drivers/xen/xenbus/xenbus_probe_backend.c
> > +++ b/drivers/xen/xenbus/xenbus_probe_backend.c
> > @@ -248,6 +248,35 @@ static int backend_probe_and_watch(struct notifier_block *notifier,
> > return NOTIFY_DONE;
> > }
> >
> > +static int xenbus_backend_reclaim(struct device *dev, void *data)
>
> No need for the xenbus_ prefix since it's a static function, ie:
> backend_reclaim_memory should be fine IMO.
Agreed, will change the name in the next version.
>
> > +{
> > + struct xenbus_driver *drv;
>
> I've asked for this variable to be constified in v5, is it not
> possible to make it const?
Sorry, my mistake... I was difinitely too hurry.
>
> > +
> > + if (!dev->driver)
> > + return 0;
> > + drv = to_xenbus_driver(dev->driver);
> > + if (drv && drv->reclaim)
> > + drv->reclaim(to_xenbus_device(dev));
> > + return 0;
> > +}
> > +
> > +/*
> > + * Returns 0 always because we are using shrinker to only detect memory
> > + * pressure.
> > + */
> > +static unsigned long xenbus_backend_shrink_count(struct shrinker *shrinker,
> > + struct shrink_control *sc)
> > +{
> > + bus_for_each_dev(&xenbus_backend.bus, NULL, NULL,
> > + xenbus_backend_reclaim);
> > + return 0;
> > +}
> > +
> > +static struct shrinker xenbus_backend_shrinker = {
>
> I would drop the xenbus prefix, and I think it's not possible to
> constify this due to register_shrinker expecting a non-const
> parameter?
Yes, constifying it results in another compile warning. Will drop the prefix.
>
> > + .count_objects = xenbus_backend_shrink_count,
> > + .seeks = DEFAULT_SEEKS,
> > +};
> > +
> > static int __init xenbus_probe_backend_init(void)
> > {
> > static struct notifier_block xenstore_notifier = {
> > @@ -264,6 +293,9 @@ static int __init xenbus_probe_backend_init(void)
> >
> > register_xenstore_notifier(&xenstore_notifier);
> >
> > + if (register_shrinker(&xenbus_backend_shrinker))
> > + pr_warn("shrinker registration failed\n");
>
> Can you add a xenbus prefix to the error message? Or else it's hard to
> know which subsystem is complaining when you see such message on the
> log. ie: "xenbus: shrinker ..."
Because we have #define `pr_fmt(fmt) KBUILD_MODNAME ": " fmt` in the beginning
of the file, the message will have a proper prefix.
>
> > +
> > return 0;
> > }
> > subsys_initcall(xenbus_probe_backend_init);
> > diff --git a/include/xen/xenbus.h b/include/xen/xenbus.h
> > index 869c816d5f8c..196260017666 100644
> > --- a/include/xen/xenbus.h
> > +++ b/include/xen/xenbus.h
> > @@ -104,6 +104,7 @@ struct xenbus_driver {
> > struct device_driver driver;
> > int (*read_otherend_details)(struct xenbus_device *dev);
> > int (*is_ready)(struct xenbus_device *dev);
> > + void (*reclaim)(struct xenbus_device *dev);
>
> reclaim_memory (if Juergen agrees).
Okay.
Thanks,
SeongJae Park
>
> Thanks, Roger.
>
next prev parent reply other threads:[~2019-12-11 12:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 4:24 [PATCH v6 0/2] xenbus/backend: Add a memory pressure handler callback SeongJae Park
2019-12-11 4:26 ` [PATCH v6 1/3] xenbus/backend: Add " SeongJae Park
2019-12-11 11:46 ` Roger Pau Monné
2019-12-11 12:20 ` SeongJae Park [this message]
2019-12-11 12:30 ` Jürgen Groß
2019-12-11 4:27 ` [PATCH v6 2/3] xen/blkback: Squeeze page pools if a memory pressure is detected SeongJae Park
2019-12-11 4:27 ` [PATCH v6 3/3] xen/blkback: Remove unnecessary static variable name prefixes SeongJae Park
2019-12-11 11:56 ` Roger Pau Monné
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=20191211122011.16231-1-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--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=pdurrant@amazon.com \
--cc=roger.pau@citrix.com \
--cc=sjpark@amazon.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).