From: "zhangliang (AG)" <zhangliang5@huawei.com>
To: David Hildenbrand <david@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<wangzhigang17@huawei.com>, Matthew Wilcox <willy@infradead.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [PATCH] mm: reuse the unshared swapcache page in do_wp_page
Date: Mon, 17 Jan 2022 21:31:52 +0800 [thread overview]
Message-ID: <b6df4f7f-c080-ad6c-d1ad-098115f016f3@huawei.com> (raw)
In-Reply-To: <9cd7eee2-91fd-ddb8-e47d-e8585e5baa05@redhat.com>
Sure, I will do that :)
On 2022/1/17 20:58, David Hildenbrand wrote:
> On 17.01.22 03:11, zhangliang (AG) wrote:
>> Hi, thank you very much for your patient reply, and I completely agree with the viewpoint from you and Linus about COW and reuse_swap_page(). :)
>>
>
> If you have some sparse cycles, it would be great if you could see if
>
> https://github.com/davidhildenbrand/linux/tree/reuse_swap_page
>
> works as expected as well for your setup.
>
--
Best Regards,
Liang Zhang
next prev parent reply other threads:[~2022-01-17 13:31 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 14:03 [PATCH] mm: reuse the unshared swapcache page in do_wp_page Liang Zhang
2022-01-13 14:39 ` Matthew Wilcox
2022-01-13 14:46 ` David Hildenbrand
2022-01-13 15:02 ` Matthew Wilcox
2022-01-13 15:04 ` David Hildenbrand
2022-01-13 16:37 ` Linus Torvalds
2022-01-13 16:48 ` David Hildenbrand
2022-01-13 17:14 ` Linus Torvalds
2022-01-13 17:25 ` David Hildenbrand
2022-01-13 17:44 ` Linus Torvalds
2022-01-13 17:55 ` David Hildenbrand
2022-01-13 18:55 ` Linus Torvalds
2022-01-13 21:07 ` Matthew Wilcox
2022-01-13 22:21 ` Linus Torvalds
2022-01-14 5:00 ` zhangliang (AG)
2022-01-14 11:23 ` David Hildenbrand
2022-01-17 2:11 ` zhangliang (AG)
2022-01-17 12:58 ` David Hildenbrand
2022-01-17 13:31 ` zhangliang (AG) [this message]
2022-01-20 14:15 ` David Hildenbrand
2022-01-20 14:39 ` Matthew Wilcox
2022-01-20 15:26 ` David Hildenbrand
2022-01-20 15:36 ` Matthew Wilcox
2022-01-20 15:39 ` David Hildenbrand
2022-01-20 15:45 ` Matthew Wilcox
2022-01-20 15:51 ` David Hildenbrand
2022-01-20 16:09 ` Matthew Wilcox
2022-01-20 16:35 ` David Hildenbrand
2022-01-20 15:37 ` Linus Torvalds
2022-01-20 15:46 ` David Hildenbrand
2022-01-20 17:22 ` Linus Torvalds
2022-01-20 17:49 ` David Hildenbrand
2022-01-20 17:48 ` Nadav Amit
2022-01-20 18:00 ` David Hildenbrand
2022-01-20 18:11 ` Nadav Amit
2022-01-20 18:19 ` David Hildenbrand
2022-01-20 19:55 ` David Hildenbrand
2022-01-20 20:07 ` Matthew Wilcox
2022-01-20 20:09 ` David Hildenbrand
2022-01-20 20:37 ` David Hildenbrand
2022-01-20 20:46 ` Nadav Amit
2022-01-20 20:49 ` David Hildenbrand
2022-01-21 9:01 ` David Hildenbrand
2022-01-21 17:43 ` Nadav Amit
2022-01-20 20:18 ` David Hildenbrand
2022-01-14 3:29 ` zhangliang (AG)
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=b6df4f7f-c080-ad6c-d1ad-098115f016f3@huawei.com \
--to=zhangliang5@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=wangzhigang17@huawei.com \
--cc=willy@infradead.org \
/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 NNTP newsgroup(s).