From: Michal Hocko <mhocko@kernel.org>
To: Yang Shi <shy828301@gmail.com>
Cc: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
cgroups@vger.kernel.org,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH RFC] mm/memcontrol: reclaim severe usage over high limit in get_user_pages loop
Date: Mon, 29 Jul 2019 20:48:50 +0200 [thread overview]
Message-ID: <20190729184850.GH9330@dhcp22.suse.cz> (raw)
In-Reply-To: <CAHbLzkrdj-O2uXwM8ujm90OcgjyR4nAiEbFtRGe7SOoY_fs=BA@mail.gmail.com>
On Mon 29-07-19 10:28:43, Yang Shi wrote:
[...]
> I don't worry too much about scale since the scale issue is not unique
> to background reclaim, direct reclaim may run into the same problem.
Just to clarify. By scaling problem I mean 1:1 kswapd thread to memcg.
You can have thousands of memcgs and I do not think we really do want
to create one kswapd for each. Once we have a kswapd thread pool then we
get into a tricky land where a determinism/fairness would be non trivial
to achieve. Direct reclaim, on the other hand is bound by the workload
itself.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-07-29 18:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 12:29 [PATCH RFC] mm/memcontrol: reclaim severe usage over high limit in get_user_pages loop Konstantin Khlebnikov
2019-07-29 9:17 ` Michal Hocko
2019-07-29 9:40 ` Konstantin Khlebnikov
2019-07-29 10:33 ` Michal Hocko
2019-07-29 11:24 ` Konstantin Khlebnikov
2019-07-29 17:28 ` Yang Shi
2019-07-29 18:48 ` Michal Hocko [this message]
2019-08-01 21:00 ` Yang Shi
2019-08-02 9:35 ` Michal Hocko
2019-08-02 18:56 ` Yang Shi
2019-08-05 14:32 ` Michal Hocko
2019-08-05 19:24 ` Shakeel Butt
2019-08-06 3:28 ` Yang Shi
2019-08-06 7:05 ` Michal Hocko
2019-07-29 15:49 ` Johannes Weiner
2019-07-29 18:55 ` Michal Hocko
2019-08-02 9:40 ` Michal Hocko
2019-08-02 10:01 ` Konstantin Khlebnikov
2019-08-02 11:44 ` Michal Hocko
2019-08-06 7:07 ` Michal Hocko
2019-08-06 7:19 ` Konstantin Khlebnikov
2019-08-06 7:36 ` Michal Hocko
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=20190729184850.GH9330@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=vdavydov.dev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.