Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38;
MIME-Version: 1.0
References: <20231106231158.380730-1-nphamcs@gmail.com> <CAF8kJuPXBLpG2d4sje6ntrA+U-AnLzu3sNpJK02YxNcg04YNng@mail.gmail.com>
 <CAKEwX=OgN_xQWrp_OYkK1BRq3DFW4he9OSycdjBm0BNy+vpPAg@mail.gmail.com>
 <CAF8kJuN--EUY95O1jpV39yv5FDu0OYanY6SZeBPk5ng4kRyrjA@mail.gmail.com>
 <CAKEwX=PT=5nvLhUyMmi=hq0_2H-4kmO9tOdqFvHEtaWF+e8M1Q@mail.gmail.com> <20231114145040.4b90d49d4ace1621c87f9c79@linux-foundation.org>
In-Reply-To: <20231114145040.4b90d49d4ace1621c87f9c79@linux-foundation.org>
From:   Nhat Pham <nphamcs@gmail.com>
Date:   Wed, 15 Nov 2023 12:25:50 -0500
Message-ID: <CAKEwX=Nhfd3J03weE2oiGQdV_sPsuPtB6NjvuSYRZBq4Fq0+9g@mail.gmail.com>
Subject: Re: [PATCH v4] zswap: memcontrol: implement zswap writeback disabling
To:     Andrew Morton <akpm@linux-foundation.org>
Cc:     Chris Li <chrisl@kernel.org>, Dan Streetman <ddstreet@ieee.org>,
        Domenico Cerasuolo <cerasuolodomenico@gmail.com>,
        Hugh Dickins <hughd@google.com>,
        Johannes Weiner <hannes@cmpxchg.org>,
        Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Seth Jennings <sjenning@redhat.com>,
        Shakeel Butt <shakeelb@google.com>,
        Vitaly Wool <vitaly.wool@konsulko.com>,
        Yosry Ahmed <yosryahmed@google.com>, corbet@lwn.net,
        david@ixit.cz, kernel-team@meta.com, linux-doc@vger.kernel.org,
        linux-mm <linux-mm@kvack.org>, lizefan.x@bytedance.com,
        mhocko@kernel.org, muchun.song@linux.dev, roman.gushchin@linux.dev,
        rppt@kernel.org, senozhatsky@chromium.org, tj@kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Tue, Nov 14, 2023 at 5:50=E2=80=AFPM Andrew Morton <akpm@linux-foundatio=
n.org> wrote:
>
> On Sat, 11 Nov 2023 16:06:58 -0800 Nhat Pham <nphamcs@gmail.com> wrote:
>
> > It's a bit of a micro-optimization indeed. But if for some reason I nee=
d
> > to send v5 or a fixlet, I'll keep this in mind!
>
> I'm seeing a lot of rejects against current mainline, so yes please.

I should have been clearer - this patch is to be applied on top of the
shrinker series (which is still under review). I originally included a comm=
ent
in the patch log, but it must have been accidentally dropped when I reworke=
d
the patch according to Chris' and Johannes' suggestions.

Nevertheless, I have rebased it on top of current mm-unstable
(with the shrinker series on top), then sent out as v5 (with the second
suggestion from Chris Li) just in case.

Let me know if there are still issues! My apologies for the inconvenience
and lack of clarity.