[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231006060245.7411-1-mark-pk.tsai@mediatek.com>
Date: Fri, 6 Oct 2023 14:02:40 +0800
From: Mark-PK Tsai <mark-pk.tsai@...iatek.com>
To: Minchan Kim <minchan@...nel.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
CC: <yj.chiang@...iatek.com>, Mark-PK Tsai <mark-pk.tsai@...iatek.com>,
<linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>
Subject: [PATCH] zsmalloc: use copy_page for full page copy
Some architectures have implemented optimized
copy_page for full page copying, such as arm.
On my arm platform, use the copy_page helper
for single page copying is about 10 percent faster
than memcpy.
Signed-off-by: Mark-PK Tsai <mark-pk.tsai@...iatek.com>
---
mm/zsmalloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
index c743ce7a5f49..b1c0dad7f4cf 100644
--- a/mm/zsmalloc.c
+++ b/mm/zsmalloc.c
@@ -1839,7 +1839,7 @@ static int zs_page_migrate(struct page *newpage, struct page *page,
* Here, any user cannot access all objects in the zspage so let's move.
*/
d_addr = kmap_atomic(newpage);
- memcpy(d_addr, s_addr, PAGE_SIZE);
+ copy_page(d_addr, s_addr);
kunmap_atomic(d_addr);
for (addr = s_addr + offset; addr < s_addr + PAGE_SIZE;
--
2.18.0
Powered by blists - more mailing lists