From: Konstantin Khlebnikov <koct9i@gmail.com>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Vladimir Davydov <vdavydov@virtuozzo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Naoya Horiguchi <nao.horiguchi@gmail.com>
Subject: Re: [PATCH v1] tools/vm/page-types.c: remove memset() in walk_pfn()
Date: Wed, 9 Mar 2016 07:28:21 +0300 [thread overview]
Message-ID: <CALYGNiPSHuZNgh33zy3KWrt0Y0Mt35HPeRxGPCZctO9aMQ=6Ow@mail.gmail.com> (raw)
In-Reply-To: <20160308055834.GA9987@hori1.linux.bs1.fc.nec.co.jp>
On Tue, Mar 8, 2016 at 8:58 AM, Naoya Horiguchi
<n-horiguchi@ah.jp.nec.com> wrote:
> On Tue, Mar 08, 2016 at 08:12:09AM +0300, Konstantin Khlebnikov wrote:
>> On Tue, Mar 8, 2016 at 4:47 AM, Naoya Horiguchi
>> <n-horiguchi@ah.jp.nec.com> wrote:
>> > I found that page-types is very slow and my testing shows many timeout errors.
>> > Here's an example with a simple program allocating 1000 thps.
>> >
>> > $ time ./page-types -p $(pgrep -f test_alloc)
>> > ...
>> > real 0m17.201s
>> > user 0m16.889s
>> > sys 0m0.312s
>> >
>> > $ time ./page-types.patched -p $(pgrep -f test_alloc)
>> > ...
>> > real 0m0.182s
>> > user 0m0.046s
>> > sys 0m0.135s
>> >
>> > Most of time is spent in memset(), which isn't necessary because we check
>> > that the return of kpagecgroup_read() is equal to pages and uninitialized
>> > memory is never used. So we can drop this memset().
>>
>> These zeros are used in show_page_range() - for merging pages into ranges.
>
> Hi Konstantin,
>
> Thank you for the response. The below code does solve the problem, so that's fine.
>
> But I don't understand how the zeros are used. show_page_range() is called
> via add_page() which is called for i=0 to i=pages-1, and the buffer cgi is
> already filled for the range [i, pages-1] by kpagecgroup_read(), so even if
> without zero initialization, kpagecgroup_read() properly fills zeros, right?
> IOW, is there any problem if we don't do this zero initialization?
kpagecgroup_read() reads only if kpagecgroup were opened,
/proc/kpagecgroup might even not exist. Probably it's better to fill
them with zeros here.
Pre-memset was an optimization - it fills buffer only once instead on
each kpagecgroup_read() call.
>
> Thanks,
> Naoya Horiguchi
>
>> You could add fast-path for count=1
>>
>> @@ -633,7 +633,10 @@ static void walk_pfn(unsigned long voffset,
>> unsigned long pages;
>> unsigned long i;
>>
>> - memset(cgi, 0, sizeof cgi);
>> + if (count == 1)
>> + cgi[0] = 0;
>> + else
>> + memset(cgi, 0, sizeof cgi);
>>
>> while (count) {
>> batch = min_t(unsigned long, count, KPAGEFLAGS_BATCH);
>>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-03-09 4:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 1:47 Naoya Horiguchi
2016-03-08 5:12 ` Konstantin Khlebnikov
2016-03-08 5:58 ` Naoya Horiguchi
2016-03-09 4:28 ` Konstantin Khlebnikov [this message]
2016-03-09 5:22 ` Naoya Horiguchi
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='CALYGNiPSHuZNgh33zy3KWrt0Y0Mt35HPeRxGPCZctO9aMQ=6Ow@mail.gmail.com' \
--to=koct9i@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=nao.horiguchi@gmail.com \
--cc=vdavydov@virtuozzo.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