All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Herrenschmidt, Benjamin" <benh@amazon.com>
To: "Agarwal, Anchal" <anchalag@amazon.com>,
	"mhocko@suse.com" <mhocko@suse.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"bugzilla-daemon@bugzilla.kernel.org"
	<bugzilla-daemon@bugzilla.kernel.org>,
	"paulfurtado91@gmail.com" <paulfurtado91@gmail.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [Bug 207273] New: cgroup with 1.5GB limit and 100MB rss usage OOM-kills processes due to page cache usage after upgrading to kernel 5.4
Date: Thu, 19 Aug 2021 09:41:11 +0000	[thread overview]
Message-ID: <f24eac1b099ac62580f66c02897aee7ea65229bd.camel@amazon.com> (raw)
In-Reply-To: <YR4l41Wn4DjdDVPl@dhcp22.suse.cz>

On Thu, 2021-08-19 at 11:35 +0200, Michal Hocko wrote:
> 
> On Wed 11-08-21 19:41:23, Anchal Agarwal wrote:
> > A gentle ping on this issue!
> 
> Sorry, I am currently swamped by other stuff and will be offline next
> week. I still try to keep this on my todo list and will try to get
> back to this hopefully soon.

Hi Michal !

Thanks for your reply ! Enjoy your time off !

Cheers,
Ben.


      reply	other threads:[~2021-08-19  9:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-207273-27@https.bugzilla.kernel.org/>
2020-04-15  4:25 ` [Bug 207273] New: cgroup with 1.5GB limit and 100MB rss usage OOM-kills processes due to page cache usage after upgrading to kernel 5.4 Andrew Morton
2020-04-15  6:50   ` Michal Hocko
2020-04-15  8:34     ` Paul Furtado
2020-04-15  9:44       ` Michal Hocko
2021-08-06 20:42         ` Anchal Agarwal
2021-08-11 19:41           ` Anchal Agarwal
2021-08-19  9:35             ` Michal Hocko
2021-08-19  9:41               ` Herrenschmidt, Benjamin [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=f24eac1b099ac62580f66c02897aee7ea65229bd.camel@amazon.com \
    --to=benh@amazon.com \
    --cc=akpm@linux-foundation.org \
    --cc=anchalag@amazon.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=paulfurtado91@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.