From: xu xin <xu.xin.sc@gmail.com>
To: david@redhat.com
Cc: akpm@linux-foundation.org, imbrenda@linux.ibm.com,
jiang.xuexin@zte.com.cn, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ran.xiaokai@zte.com.cn, xu.xin.sc@gmail.com,
xu.xin16@zte.com.cn, yang.yang29@zte.com.cn
Subject: Re: [PATCH v8 1/6] ksm: support unsharing KSM-placed zero pages
Date: Tue, 23 May 2023 21:55:47 +0800 [thread overview]
Message-ID: <20230523135547.6819-1-xu.xin16@zte.com.cn> (raw)
In-Reply-To: <1925d301-462d-6b33-8867-4e1646b2dbd6@redhat.com>
Excuse me, I'm wondering why using inline here instead of macro is better.
Thanks! :)
Thanks for reviews.
next prev parent reply other threads:[~2023-05-23 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 10:42 [PATCH v8 0/6] ksm: support tracking KSM-placed zero-pages yang.yang29
[not found] ` <20230522104908.3999-1-yang.yang29@zte.com.cn>
2023-05-23 9:41 ` [PATCH v8 1/6] ksm: support unsharing KSM-placed zero pages David Hildenbrand
2023-05-23 13:55 ` xu xin [this message]
2023-05-23 13:57 ` xu xin
2023-05-23 14:00 ` David Hildenbrand
2023-05-23 14:11 ` xu xin
[not found] ` <20230522105229.4066-1-yang.yang29@zte.com.cn>
2023-05-23 9:47 ` [PATCH v8 2/6] ksm: count all zero pages placed by KSM David Hildenbrand
2023-05-23 9:51 ` David Hildenbrand
[not found] ` <20230522105305.4126-1-yang.yang29@zte.com.cn>
2023-05-23 9:55 ` [PATCH v8 3/6] ksm: add ksm zero pages for each process David Hildenbrand
[not found] ` <20230522105335.4176-1-yang.yang29@zte.com.cn>
2023-05-23 9:58 ` [PATCH v8 4/6] ksm: add documentation for ksm zero pages David Hildenbrand
[not found] ` <20230522105402.4225-1-yang.yang29@zte.com.cn>
2023-05-23 10:01 ` [PATCH v8 5/6] ksm: update the calculation of KSM profit David Hildenbrand
[not found] ` <20230522105433.4277-1-yang.yang29@zte.com.cn>
2023-05-23 10:15 ` [PATCH v8 6/6] selftest: add a testcase of ksm zero pages David Hildenbrand
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=20230523135547.6819-1-xu.xin16@zte.com.cn \
--to=xu.xin.sc@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=jiang.xuexin@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ran.xiaokai@zte.com.cn \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
/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