From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: David Hildenbrand <david@redhat.com>,
kernel test robot <oliver.sang@intel.com>,
Peter Xu <peterx@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Huacai Chen <chenhuacai@kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>,
Matthew Wilcox <willy@infradead.org>,
Nathan Chancellor <nathan@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
WANG Xuerui <kernel@xen0n.name>, <linux-mm@kvack.org>,
<ying.huang@intel.com>, <feng.tang@intel.com>
Subject: Re: [linus:master] [mm] c0bff412e6: stress-ng.clone.ops_per_sec -2.9% regression
Date: Thu, 1 Aug 2024 15:44:13 +0800 [thread overview]
Message-ID: <99a5e8b5-6040-4de7-a185-7a39c16ae0fa@intel.com> (raw)
In-Reply-To: <90477952-fde2-41d7-8ff4-2102c45e341d@redhat.com>
Hi David,
On 8/1/2024 2:49 PM, David Hildenbrand wrote:
> We now have to do a page_folio(page) and then test for hugetlb.
>
> return folio_test_hugetlb(page_folio(page));
>
> Nowadays, folio_test_hugetlb() will be faster than at c0bff412e6 times,
> so maybe at least part of the overhead is gone.
This is great. We will check the trend to know whether it's recovered
in some level.
Regards
Yin, Fengwei
next prev parent reply other threads:[~2024-08-01 7:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 5:00 kernel test robot
2024-07-30 8:11 ` David Hildenbrand
2024-08-01 6:39 ` Yin, Fengwei
2024-08-01 6:49 ` David Hildenbrand
2024-08-01 7:44 ` Yin, Fengwei [this message]
2024-08-01 7:54 ` David Hildenbrand
2024-08-01 13:30 ` Mateusz Guzik
2024-08-01 13:34 ` David Hildenbrand
2024-08-01 13:37 ` Mateusz Guzik
2024-08-01 13:44 ` David Hildenbrand
2024-08-12 4:43 ` Yin Fengwei
2024-08-12 4:49 ` Mateusz Guzik
2024-08-12 8:12 ` David Hildenbrand
2024-08-12 8:18 ` Mateusz Guzik
2024-08-12 8:23 ` David Hildenbrand
2024-08-13 7:09 ` Yin Fengwei
2024-08-13 7:14 ` Mateusz Guzik
2024-08-14 3:02 ` Yin Fengwei
2024-08-14 4:10 ` Mateusz Guzik
2024-08-14 9:45 ` David Hildenbrand
2024-08-14 11:06 ` Mateusz Guzik
2024-08-14 12:02 ` 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=99a5e8b5-6040-4de7-a185-7a39c16ae0fa@intel.com \
--to=fengwei.yin@intel.com \
--cc=akpm@linux-foundation.org \
--cc=chenhuacai@kernel.org \
--cc=david@redhat.com \
--cc=feng.tang@intel.com \
--cc=jgg@nvidia.com \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=nathan@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterx@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.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