From: Christoph Hellwig <hch@lst.de>
To: Liu Shixin <liushixin2@huawei.com>
Cc: Seth Jennings <sjenning@redhat.com>,
Dan Streetman <ddstreet@ieee.org>,
Vitaly Wool <vitaly.wool@konsulko.com>,
Andrew Morton <akpm@linux-foundation.org>,
Nathan Chancellor <nathan@kernel.org>,
Christoph Hellwig <hch@lst.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH -next v4 1/6] Revert "frontswap: remove support for multiple ops"
Date: Tue, 30 Aug 2022 07:05:59 +0200 [thread overview]
Message-ID: <20220830050559.GA23877@lst.de> (raw)
In-Reply-To: <20220829132302.3367054-2-liushixin2@huawei.com>
On Mon, Aug 29, 2022 at 09:22:57PM +0800, Liu Shixin wrote:
> This reverts commit 1da0d94a3ec8c5f3793b7be8538b55e60ebeefe3.
Err, no, this is a way to big hammer and going in the wrong way.
If we can't have a sane way to fix it, the fix is just to remove
the now rather pointless fontswap abstraction entirely.
I'm on vacation this week, but I'll look into it ASAP once back.
next prev parent reply other threads:[~2022-08-30 5:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 13:22 [PATCH -next v4 0/6] Delay the initializaton of zswap Liu Shixin
2022-08-29 13:22 ` [PATCH -next v4 1/6] Revert "frontswap: remove support for multiple ops" Liu Shixin
2022-08-30 5:05 ` Christoph Hellwig [this message]
2022-08-29 13:22 ` [PATCH -next v4 2/6] Revert "mm: mark swap_lock and swap_active_head static" Liu Shixin
2022-08-29 13:22 ` [PATCH -next v4 3/6] Revert "frontswap: simplify frontswap_register_ops" Liu Shixin
2022-08-29 13:23 ` [PATCH -next v4 4/6] mm/zswap: replace zswap_init_{started/failed} with zswap_init_state Liu Shixin
2022-08-29 13:23 ` [PATCH -next v4 5/6] mm/zswap: delay the initializaton of zswap until the first enablement Liu Shixin
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=20220830050559.GA23877@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liushixin2@huawei.com \
--cc=nathan@kernel.org \
--cc=sjenning@redhat.com \
--cc=vitaly.wool@konsulko.com \
--cc=wangkefeng.wang@huawei.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