From: Huang Ying <ying.huang@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Huang Ying" <ying.huang@intel.com>,
Hugh Dickins <hughd@google.com>,
Alistair Popple <apopple@nvidia.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
David Hildenbrand <david@redhat.com>,
Mel Gorman <mgorman@techsingularity.net>,
Miaohe Lin <linmiaohe@huawei.com>,
Minchan Kim <minchan@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Yang Shi <shy828301@gmail.com>, Yu Zhao <yuzhao@google.com>,
Kairui Song <kasong@tencent.com>,
Barry Song <v-songbaohua@oppo.com>, Chris Li <chrisl@kernel.org>,
Yosry Ahmed <yosryahmed@google.com>
Subject: [PATCH 0/3] mm,swap: cleanup VMA based swap readahead window calculation
Date: Fri, 31 May 2024 16:12:27 +0800 [thread overview]
Message-ID: <20240531081230.310128-1-ying.huang@intel.com> (raw)
From: "Huang Ying" <ying.huang@intel.com>
When VMA based swap readahead is introduced in commit ec560175c0b6
("mm, swap: VMA based swap readahead"), "struct vma_swap_readahead" is
defined to describe the readahead window. Because we wanted to save
the PTE entries in the struct at that time. But after commit
4f8fcf4ced0b ("mm/swap: swap_vma_readahead() do the
pte_offset_map()"), we no longer save PTE entries in the struct. The
size of the struct becomes so small, that it's better to use the
fields of the struct directly. This can simplify the code to improve
the code readability. The line number of source code reduces too.
A theoretical underflow issue and some related code cleanup is done in
the series too.
Best Regards,
Huang, Ying
next reply other threads:[~2024-05-31 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 8:12 Huang Ying [this message]
2024-05-31 8:12 ` [PATCH 1/3] mm,swap: fix a theoretical underflow in " Huang Ying
2024-05-31 8:12 ` [PATCH 2/3] mm,swap: remove struct vma_swap_readahead Huang Ying
2024-05-31 8:12 ` [PATCH 3/3] mm,swap: simplify VMA based swap readahead window calculation 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=20240531081230.310128-1-ying.huang@intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=apopple@nvidia.com \
--cc=chrisl@kernel.org \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=kasong@tencent.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=minchan@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=v-songbaohua@oppo.com \
--cc=yosryahmed@google.com \
--cc=yuzhao@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