From: Wei Yang <richard.weiyang@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, dan.j.williams@intel.com,
mhocko@suse.com, linux-mm@kvack.org
Subject: Re: [RFC PATCH] mm: add a vma to vmacache when addr overlaps the vma range
Date: Tue, 16 Oct 2018 14:17:13 +0000 [thread overview]
Message-ID: <20181016141713.qtry7cvtap6wzmj4@master> (raw)
In-Reply-To: <20181016135404.GA13818@bombadil.infradead.org>
On Tue, Oct 16, 2018 at 06:54:04AM -0700, Matthew Wilcox wrote:
>On Tue, Oct 16, 2018 at 09:47:12PM +0800, Wei Yang wrote:
>> Based on my understanding, this change would put more accurate vma entry in the
>> cache, which means reduce unnecessary vmacache update and vmacache find.
>>
>> But the test result is not as expected. From the original changelog, I don't
>> see the explanation to add this non-overlap entry into the vmacache, so
>> curious about why this performs a little better than putting an overlapped
>> entry.
>
>What makes you think this performs any differently for this test-case?
>The numbers all seem to fall within a "reasonable variation" range to me.
>You're going to need to do some statistics (with a much larger sample
>size) to know whether there's any difference at all.
>
Matthew,
Thanks for your comment.
I use this test-case because I have little experience in performance
test and I see the original author lists the hit-rate improvement in
kernel build test.
I am thinking to evaluate the cache hit-rate, while I don't know how to
gather the statistic.
If you could give me some hint on the statistics gathering or a more
proper test case, I would appreciate a lot.
BTW, I don't get your point on "a much larger sample size". To map a
larger memory area? I lost at this point.
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2018-10-16 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 13:47 [RFC PATCH] mm: add a vma to vmacache when addr overlaps the vma range Wei Yang
2018-10-16 13:54 ` Matthew Wilcox
2018-10-16 14:17 ` Wei Yang [this message]
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=20181016141713.qtry7cvtap6wzmj4@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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).