From: Yu Zhao <yuzhao@google.com>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Yue Zhao <findns94@gmail.com>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-mm@kvack.org, Tejun Heo <tj@kernel.org>,
Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Jonathan Corbet <corbet@lwn.net>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeelb@google.com>,
Muchun Song <muchun.song@linux.dev>,
David Hildenbrand <david@redhat.com>,
Chris Li <chrisl@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Yosry Ahmed <yosryahmed@google.com>,
Hugh Dickins <hughd@google.com>,
Dan Schatzberg <schatzberg.dan@gmail.com>
Subject: Re: [PATCH v6 0/2] Add swappiness argument to memory.reclaim
Date: Tue, 11 Jun 2024 17:10:12 -0600 [thread overview]
Message-ID: <CAOUHufafhx+3QE1CSQpctOm8NjQRuHLT+jyK=mf7c2dgFAn4+g@mail.gmail.com> (raw)
In-Reply-To: <mpshgxmd3c3gpxltlvquw7zvhq5rvukcws55yo7womgogjxu7q@4p7dr66ctwxh>
On Tue, Jun 11, 2024 at 4:50 PM Shakeel Butt <shakeel.butt@linux.dev> wrote:
>
> On Tue, Jun 11, 2024 at 12:48:07PM GMT, Andrew Morton wrote:
> > On Tue, 11 Jun 2024 12:25:24 -0700 Shakeel Butt <shakeel.butt@linux.dev> wrote:
> >
> > > Hi folks,
> > >
> > > This series has been in the mm-unstable for several months. Are there
> > > any remaining concerns here otherwise can we please put this in the
> > > mm-stable branch to be merged in the next Linux release?
> >
> > The review didn't go terribly well so I parked the series awaiting more
> > clarity. Although on rereading, it seems that Yu Zhao isn't seeing any
> > blocking issues?
> >
>
> Yu, please share if you have any strong concern in merging this series?
I don't remember I had any strong concerns. In fact, I don't remember
what I commented on.
Let me go back to the previous discussion and see why it was stalled.
Will get back to you soon.
prev parent reply other threads:[~2024-06-11 23:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 16:48 Dan Schatzberg
2024-01-03 16:48 ` [PATCH v6 1/2] mm: add defines for min/max swappiness Dan Schatzberg
2024-01-03 16:48 ` [PATCH v6 2/2] mm: add swapiness= arg to memory.reclaim Dan Schatzberg
2024-01-03 17:19 ` Yu Zhao
2024-01-03 18:19 ` Dan Schatzberg
2024-01-04 1:07 ` Yu Zhao
2024-01-04 8:48 ` Michal Hocko
2024-01-09 23:54 ` Yu Zhao
2024-01-10 10:32 ` Michal Hocko
2024-01-04 1:17 ` Yu Zhao
2024-01-04 10:09 ` Michal Hocko
2024-01-09 23:57 ` Yu Zhao
2024-06-11 19:25 ` [PATCH v6 0/2] Add swappiness argument " Shakeel Butt
2024-06-11 19:31 ` Yosry Ahmed
2024-06-11 19:48 ` Andrew Morton
2024-06-11 22:50 ` Shakeel Butt
2024-06-11 23:10 ` Yu Zhao [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='CAOUHufafhx+3QE1CSQpctOm8NjQRuHLT+jyK=mf7c2dgFAn4+g@mail.gmail.com' \
--to=yuzhao@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chrisl@kernel.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=findns94@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=schatzberg.dan@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=shakeelb@google.com \
--cc=tj@kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox