From: Chris Li <chrisl@kernel.org>
To: Baoquan He <bhe@redhat.com>
Cc: Barry Song <21cnbao@gmail.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
baohua@kernel.org, kasong@tencent.com, nphamcs@gmail.com,
shikemeng@huaweicloud.com, youngjun.park@lge.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] mm/swap: use swap_ops to register swap device's methods
Date: Wed, 8 Apr 2026 09:27:27 -0700 [thread overview]
Message-ID: <CACePvbV66RRGg-q8mBE6sPa08drVc_NV_HW5QjrUw+hL+=JDaw@mail.gmail.com> (raw)
In-Reply-To: <adZ4LehwC9KisuXf@MiWiFi-R3L-srv>
On Wed, Apr 8, 2026 at 8:46 AM Baoquan He <bhe@redhat.com> wrote:
> Both is fine to me. I will change to do the checking in
> setup_swap_ops(). By the way, I tend to rename setup_swap_ops() as
> init_swap_ops(), is it OK to you?
Sure. Eventually we will need a function to detect the swap device and
decide which type of swap ops to use. This is just like in the file
system after reading the super block. The kernel need to probe which
file system driver to load.
Chris
next prev parent reply other threads:[~2026-04-08 16:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 7:58 [PATCH v2 0/3] " Barry Song
2026-03-28 7:58 ` [PATCH v2 1/3] mm/swap: rename mm/page_io.c to mm/swap_io.c Barry Song
2026-03-29 14:31 ` Chris Li
2026-03-28 7:58 ` [PATCH v2 2/3] mm/swap: use swap_ops to register swap device's methods Barry Song
2026-03-29 10:49 ` kernel test robot
2026-03-29 11:44 ` Barry Song
2026-03-29 11:10 ` kernel test robot
2026-03-31 3:30 ` Chris Li
2026-03-31 9:21 ` Barry Song
2026-03-31 16:10 ` Chris Li
2026-04-08 6:11 ` Baoquan He
2026-04-08 9:26 ` Chris Li
2026-04-08 15:45 ` Baoquan He
2026-04-08 16:27 ` Chris Li [this message]
2026-03-28 7:58 ` [PATCH v2 3/3] mm/swap_io.c: rename swap_writepage_* to swap_write_folio_* Barry Song
2026-03-29 14:31 ` Chris Li
2026-03-30 0:54 ` [PATCH v2 0/3] mm/swap: use swap_ops to register swap device's methods Baoquan He
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='CACePvbV66RRGg-q8mBE6sPa08drVc_NV_HW5QjrUw+hL+=JDaw@mail.gmail.com' \
--to=chrisl@kernel.org \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=bhe@redhat.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=shikemeng@huaweicloud.com \
--cc=youngjun.park@lge.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