From: Michal Hocko <mhocko@kernel.org>
To: Sasha Levin <Alexander.Levin@microsoft.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] memcg: fix per_node_info cleanup
Date: Tue, 10 Apr 2018 22:37:49 +0200 [thread overview]
Message-ID: <20180410203749.GW21835@dhcp22.suse.cz> (raw)
In-Reply-To: <20180410175510.GH2341@sasha-vm>
On Tue 10-04-18 17:55:13, Sasha Levin wrote:
> On Tue, Apr 10, 2018 at 04:01:32PM +0200, Michal Hocko wrote:
> >On Tue 10-04-18 13:50:30, Sasha Levin wrote:
> >> Hi,
> >>
> >> [This is an automated email]
> >>
> >> This commit has been processed because it contains a "Fixes:" tag,
> >> fixing commit: 00f3ca2c2d66 mm: memcontrol: per-lruvec stats infrastructure.
> >
> >Yes and the changelog states conditions which are quite hard to achieve
> >to have this patch in the stable tree. So I am not really convinced it
> >is worth backporting even though the patch itself is trivial.
>
> Quite hard to achieve, but the changelog also indicated that this was
> actually hit and is not just theoretical. Is there something that will
> prevent this from happening on "real" workloads?
Well, small allocations do not really fail and it would take to
configure a really large NUMA system to achieve the same. So I am
skeptical.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2018-04-10 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 10:09 [PATCH] memcg: fix per_node_info cleanup Michal Hocko
2018-04-06 10:09 ` Michal Hocko
2018-04-10 13:50 ` Sasha Levin
2018-04-10 14:01 ` Michal Hocko
2018-04-10 17:55 ` Sasha Levin
2018-04-10 20:37 ` Michal Hocko [this message]
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=20180410203749.GW21835@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=Alexander.Levin@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=stable@vger.kernel.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 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.