From: Waiman Long <longman@redhat.com>
To: Michal Hocko <mhocko@kernel.org>,
kernel test robot <rong.a.chen@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Davidlohr Bueso <dbueso@suse.de>,
Kirill Tkhai <ktkhai@virtuozzo.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Matthew Wilcox <willy@infradead.org>,
Andi Kleen <ak@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org
Subject: Re: [mm/hugetlb] c77c0a8ac4: will-it-scale.per_process_ops 15.9% improvement
Date: Tue, 14 Jan 2020 09:57:14 -0500 [thread overview]
Message-ID: <bd474ca4-9f47-0ab1-f461-513789fc074d@redhat.com> (raw)
In-Reply-To: <20200114091251.GE19428@dhcp22.suse.cz>
On 1/14/20 4:12 AM, Michal Hocko wrote:
> On Tue 14-01-20 16:56:37, kernel test robot wrote:
>> Greeting,
>>
>> FYI, we noticed a 15.9% improvement of will-it-scale.per_process_ops due to commit:
>>
>>
>> commit: c77c0a8ac4c522638a8242fcb9de9496e3cdbb2d ("mm/hugetlb: defer freeing of huge pages if in non-task context")
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> This is more than surprising because the patch has only changed the
> behavior for hugetlb pages freed from the (soft)interrupt context and
> that should be a very rare event. Does the test really generate a lot of
> those?
>
Yes, I have the same question. I was not expecting to see any
performance impact.
Cheers,
Longman
next prev parent reply other threads:[~2020-01-14 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 8:56 kernel test robot
2020-01-14 9:12 ` Michal Hocko
2020-01-14 14:57 ` Waiman Long [this message]
2020-01-17 6:56 ` [LKP] " Feng Tang
2020-01-17 7:52 ` Michal Hocko
2020-01-17 14:05 ` Waiman Long
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=bd474ca4-9f47-0ab1-f461-513789fc074d@redhat.com \
--to=longman@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dbueso@suse.de \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=rong.a.chen@intel.com \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®