From: Johannes Weiner <hannes@cmpxchg.org>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
mm-commits@vger.kernel.org, yosryahmed@google.com, tj@kernel.org,
shakeelb@google.com, schatzberg.dan@gmail.com,
muchun.song@linux.dev, mhocko@kernel.org
Subject: Re: + mm-memcontrol-dont-throttle-dying-tasks-on-memoryhigh.patch added to mm-hotfixes-unstable branch
Date: Wed, 17 Jan 2024 10:56:25 -0500 [thread overview]
Message-ID: <20240117155625.GC939255@cmpxchg.org> (raw)
In-Reply-To: <Zab_tRKQzSS25ugy@P9FQF9L96D>
On Tue, Jan 16, 2024 at 02:14:13PM -0800, Roman Gushchin wrote:
> On Tue, Jan 16, 2024 at 01:45:47PM -0800, Andrew Morton wrote:
> >
> > The patch titled
> > Subject: mm: memcontrol: don't throttle dying tasks on memory.high
> > has been added to the -mm mm-hotfixes-unstable branch. Its filename is
> > mm-memcontrol-dont-throttle-dying-tasks-on-memoryhigh.patch
> >
> > This patch will shortly appear at
> > https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-memcontrol-dont-throttle-dying-tasks-on-memoryhigh.patch
>
> Hi Andrew,
>
> there is an updated version from Johannes in the same thread.
> It seems like you've picked the original version. Please, pick
> the new one instead.
Oops, yes, thanks Roman.
Andrew, it's the one I replied to privately:
https://lore.kernel.org/linux-mm/20240111192807.GA424308@cmpxchg.org/
It incorporates Roman's and Yosry's feedback on v1.
prev parent reply other threads:[~2024-01-17 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 21:45 + mm-memcontrol-dont-throttle-dying-tasks-on-memoryhigh.patch added to mm-hotfixes-unstable branch Andrew Morton
2024-01-16 22:14 ` Roman Gushchin
2024-01-17 15:56 ` Johannes Weiner [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=20240117155625.GC939255@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=mhocko@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=schatzberg.dan@gmail.com \
--cc=shakeelb@google.com \
--cc=tj@kernel.org \
--cc=yosryahmed@google.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.