From: Dan Williams <dan.j.williams@intel.com>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
"Dan Williams" <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Ira Weiny <ira.weiny@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
<linux-block@vger.kernel.org>, <nvdimm@lists.linux.dev>,
<linux-fsdevel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: RE: [PATCH 3/7] mm: factor out a swap_readpage_bdev helper
Date: Wed, 25 Jan 2023 10:30:29 -0800 [thread overview]
Message-ID: <63d17545bb932_3a36e5294ec@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20230125133436.447864-4-hch@lst.de>
Christoph Hellwig wrote:
> Split the block device case from swap_readpage into a separate helper,
> following the abstraction for file based swap and frontswap.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> mm/page_io.c | 68 +++++++++++++++++++++++++++-------------------------
> 1 file changed, 35 insertions(+), 33 deletions(-)
>
> diff --git a/mm/page_io.c b/mm/page_io.c
> index 6f7166fdc4b2bb..ce0b3638094f85 100644
> --- a/mm/page_io.c
> +++ b/mm/page_io.c
> @@ -445,44 +445,15 @@ static void swap_readpage_fs(struct page *page,
> *plug = sio;
> }
>
> -void swap_readpage(struct page *page, bool synchronous, struct swap_iocb **plug)
> +static void swap_readpage_bdev(struct page *page, bool synchronous,
> + struct swap_info_struct *sis)
> {
> struct bio *bio;
> - struct swap_info_struct *sis = page_swap_info(page);
> - bool workingset = PageWorkingset(page);
> - unsigned long pflags;
> - bool in_thrashing;
> -
> - VM_BUG_ON_PAGE(!PageSwapCache(page) && !synchronous, page);
> - VM_BUG_ON_PAGE(!PageLocked(page), page);
> - VM_BUG_ON_PAGE(PageUptodate(page), page);
> -
> - /*
> - * Count submission time as memory stall and delay. When the device
> - * is congested, or the submitting cgroup IO-throttled, submission
> - * can be a significant part of overall IO time.
> - */
> - if (workingset) {
> - delayacct_thrashing_start(&in_thrashing);
> - psi_memstall_enter(&pflags);
> - }
> - delayacct_swapin_start();
> -
> - if (frontswap_load(page) == 0) {
> - SetPageUptodate(page);
> - unlock_page(page);
> - goto out;
> - }
> -
> - if (data_race(sis->flags & SWP_FS_OPS)) {
> - swap_readpage_fs(page, plug);
> - goto out;
> - }
>
> if ((sis->flags & SWP_SYNCHRONOUS_IO) &&
> !bdev_read_page(sis->bdev, swap_page_sector(page), page)) {
> count_vm_event(PSWPIN);
> - goto out;
> + return;
> }
>
> bio = bio_alloc(sis->bdev, 1, REQ_OP_READ, GFP_KERNEL);
> @@ -509,8 +480,39 @@ void swap_readpage(struct page *page, bool synchronous, struct swap_iocb **plug)
> }
> __set_current_state(TASK_RUNNING);
> bio_put(bio);
> +}
> +
> +void swap_readpage(struct page *page, bool synchronous, struct swap_iocb **plug)
> +{
> + struct swap_info_struct *sis = page_swap_info(page);
> + bool workingset = PageWorkingset(page);
> + unsigned long pflags;
> + bool in_thrashing;
> +
> + VM_BUG_ON_PAGE(!PageSwapCache(page) && !synchronous, page);
> + VM_BUG_ON_PAGE(!PageLocked(page), page);
> + VM_BUG_ON_PAGE(PageUptodate(page), page);
> +
> + /*
> + * Count submission time as memory stall and delay. When the device
> + * is congested, or the submitting cgroup IO-throttled, submission
> + * can be a significant part of overall IO time.
> + */
> + if (workingset) {
> + delayacct_thrashing_start(&in_thrashing);
> + psi_memstall_enter(&pflags);
> + }
> + delayacct_swapin_start();
> +
> + if (frontswap_load(page) == 0) {
> + SetPageUptodate(page);
> + unlock_page(page);
> + } else if (data_race(sis->flags & SWP_FS_OPS)) {
> + swap_readpage_fs(page, plug);
> + } else {
> + swap_readpage_bdev(page, synchronous, sis);
> + }
>
> -out:
> if (workingset) {
> delayacct_thrashing_end(&in_thrashing);
> psi_memstall_leave(&pflags);
Looks good, passes tests,
Reviewed-by: Dan Williams <dan.j.williams@intel.com>
next prev parent reply other threads:[~2023-01-25 18:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 13:34 remove ->rw_page Christoph Hellwig
2023-01-25 13:34 ` [PATCH 1/7] mpage: stop using bdev_{read,write}_page Christoph Hellwig
2023-01-25 17:58 ` Dan Williams
2023-01-25 13:34 ` [PATCH 2/7] mm: remove the swap_readpage return value Christoph Hellwig
2023-01-25 15:58 ` Keith Busch
2023-01-26 5:30 ` Christoph Hellwig
2023-01-25 18:00 ` Dan Williams
2023-01-25 13:34 ` [PATCH 3/7] mm: factor out a swap_readpage_bdev helper Christoph Hellwig
2023-01-25 18:30 ` Dan Williams [this message]
2023-01-25 13:34 ` [PATCH 4/7] mm: use an on-stack bio for synchronous swapin Christoph Hellwig
2023-01-25 13:34 ` [PATCH 5/7] mm: remove the __swap_writepage return value Christoph Hellwig
2023-01-25 13:34 ` [PATCH 6/7] mm: factor out a swap_writepage_bdev helper Christoph Hellwig
2023-01-25 13:34 ` [PATCH 7/7] block: remove ->rw_page Christoph Hellwig
2023-01-25 16:28 ` Keith Busch
2023-01-26 5:30 ` Christoph Hellwig
2023-01-25 18:38 ` Dan Williams
2023-01-25 14:32 ` Jens Axboe
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=63d17545bb932_3a36e5294ec@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dave.jiang@intel.com \
--cc=hch@lst.de \
--cc=ira.weiny@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=senozhatsky@chromium.org \
--cc=vishal.l.verma@intel.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