From: Kairui Song <ryncsn@gmail.com>
To: linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Huang, Ying" <ying.huang@intel.com>,
Matthew Wilcox <willy@infradead.org>,
Chris Li <chrisl@kernel.org>, Barry Song <v-songbaohua@oppo.com>,
Ryan Roberts <ryan.roberts@arm.com>, Neil Brown <neilb@suse.de>,
Minchan Kim <minchan@kernel.org>,
David Hildenbrand <david@redhat.com>,
Hugh Dickins <hughd@google.com>,
Yosry Ahmed <yosryahmed@google.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Kairui Song <kasong@tencent.com>, Chao Yu <chao@kernel.org>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: [PATCH v5 01/12] f2fs: drop usage of page_index
Date: Fri, 10 May 2024 19:47:36 +0800 [thread overview]
Message-ID: <20240510114747.21548-2-ryncsn@gmail.com> (raw)
In-Reply-To: <20240510114747.21548-1-ryncsn@gmail.com>
From: Kairui Song <kasong@tencent.com>
page_index is needed for mixed usage of page cache and swap cache,
for pure page cache usage, the caller can just use page->index instead.
It can't be a swap cache page here, so just drop it.
[ This commit will not be needed once f2fs converted
f2fs_mpage_readpages() to use folio]
Signed-off-by: Kairui Song <kasong@tencent.com>
Cc: Chao Yu <chao@kernel.org>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
---
fs/f2fs/data.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 961e6ff77c72..c0e1459702e6 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -2057,7 +2057,7 @@ static int f2fs_read_single_page(struct inode *inode, struct page *page,
sector_t block_nr;
int ret = 0;
- block_in_file = (sector_t)page_index(page);
+ block_in_file = (sector_t)page->index;
last_block = block_in_file + nr_pages;
last_block_in_file = bytes_to_blks(inode,
f2fs_readpage_limit(inode) + blocksize - 1);
--
2.45.0
next prev parent reply other threads:[~2024-05-10 11:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 11:47 [PATCH v5 00/12] mm/swap: clean up and optimize swap cache index Kairui Song
2024-05-10 11:47 ` Kairui Song [this message]
2024-05-10 11:47 ` [PATCH v5 02/12] nilfs2: drop usage of page_index Kairui Song
2024-05-10 11:47 ` [PATCH v5 03/12] ceph: " Kairui Song
2024-05-10 11:47 ` [PATCH v5 04/12] NFS: remove nfs_page_lengthg and " Kairui Song
2024-05-10 11:47 ` [PATCH v5 05/12] cifs: drop usage of page_file_offset Kairui Song
2024-05-10 11:47 ` [PATCH v5 06/12] afs: drop usage of folio_file_pos Kairui Song
2024-05-10 11:47 ` [PATCH v5 07/12] netfs: " Kairui Song
2024-05-10 11:47 ` [PATCH v5 08/12] nfs: " Kairui Song
2024-05-10 11:47 ` [PATCH v5 09/12] mm/swap: get the swap device offset directly Kairui Song
2024-05-10 11:47 ` [PATCH v5 10/12] mm: remove page_file_offset and folio_file_pos Kairui Song
2024-05-10 11:47 ` [PATCH v5 11/12] mm: drop page_index and simplify folio_index Kairui Song
2024-05-11 5:39 ` Huang, Ying
2024-05-10 11:47 ` [PATCH v5 12/12] mm/swap: reduce swap cache search space Kairui Song
2024-05-11 5:54 ` Huang, Ying
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=20240510114747.21548-2-ryncsn@gmail.com \
--to=ryncsn@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chao@kernel.org \
--cc=chrisl@kernel.org \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=jaegeuk@kernel.org \
--cc=kasong@tencent.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=neilb@suse.de \
--cc=ryan.roberts@arm.com \
--cc=v-songbaohua@oppo.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).