linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shakeel Butt <shakeelb@google.com>
To: Greg KH <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Linux MM <linux-mm@kvack.org>
Cc: Ivan Babrou <ivan@cloudflare.com>,
	stable <stable@vger.kernel.org>,
	 kernel-team <kernel-team@cloudflare.com>
Subject: Re: Backport memcg flush improvements into 5.15
Date: Thu, 27 Jan 2022 07:41:52 -0800	[thread overview]
Message-ID: <CALvZod76vX94jG0W9f-RJGu9pSYi_uMw5BE6xfL9p30pgLShUQ@mail.gmail.com> (raw)
In-Reply-To: <YfK6gfXZZGNqsnyr@kroah.com>

+Andrew & linux-mm

On Thu, Jan 27, 2022 at 7:30 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Wed, Jan 19, 2022 at 04:15:34PM -0800, Ivan Babrou wrote:
> > Hello,
> >
> > We've seen a significant perf degradation when reading a tmpfs file
> > swapped into zram between 5.10 and 5.15. The source of the issue is:
> >
> > * aa48e47e3906: memcg: infrastructure to flush memcg stats
> >
> > There's a couple of commits that helps to bridge the gap in 5.16:
> >
> > * 11192d9c124d: memcg: flush stats only if updated
> > * fd25a9e0e23b: memcg: unify memcg stat flushing
> >
> > Both of these apply cleanly and Shakeel (the author) has okayed the
> > backport from his end. He also suggested backporting the following:
> >
> > * 5b3be698a872: memcg: better bounds on the memcg stats updates
> >
> > I personally did not test this one, but it applies cleanly, so there's
> > probably no harm. I cc'd Shakeel in case you want confirmation on
> > that. It's not a part of any tag yet.
> >
> > Please backport all three (or at least the first two) to 5.15 LTS.
>
> All now queued up, thanks!

Thanks Greg.

Adding Andrew (and linux-mm) in CC to let him know the reason for
backporting these patches to 5.15 stable tree.

>
> greg k-h


           reply	other threads:[~2022-01-27 15:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <YfK6gfXZZGNqsnyr@kroah.com>]

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=CALvZod76vX94jG0W9f-RJGu9pSYi_uMw5BE6xfL9p30pgLShUQ@mail.gmail.com \
    --to=shakeelb@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ivan@cloudflare.com \
    --cc=kernel-team@cloudflare.com \
    --cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox