From: Thomas Zimmermann <tzimmermann@suse.de>
To: Mike Kravetz <mike.kravetz@oracle.com>,
kernel test robot <rong.a.chen@intel.com>
Cc: John Donnelly <John.p.donnelly@oracle.com>,
Emil Velikov <emil.velikov@collabora.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com, ying.huang@intel.com,
feng.tang@intel.com, zhengjun.xing@intel.com
Subject: Re: [drm/mgag200] 913ec479bb: vm-scalability.throughput 26.2% improvement
Date: Sat, 29 Aug 2020 20:06:04 +0200 [thread overview]
Message-ID: <f9664139-e28c-ba8e-b4e4-d505baf9069a@suse.de> (raw)
In-Reply-To: <99c7683c-f428-378d-2b19-ef51270a5d8e@oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 2294 bytes --]
Hi
Am 27.08.20 um 16:56 schrieb Mike Kravetz:
> On 8/27/20 2:16 AM, Thomas Zimmermann wrote:
>> Hi
>>
>> Am 26.08.20 um 10:58 schrieb kernel test robot:
>>> Greeting,
>>>
>>> FYI, we noticed a 26.2% improvement of vm-scalability.throughput due to commit:
>>
>> I guess this resolves the once-measured performance penalty of similar
>> magnitude. But do we really understand these tests? When I sent out
>> patches to resolve the problem, nothing changed. And suddenly the
>> performance is back to normal.
>>
>> Best regards
>> Thomas
>>
>>>
>>>
>>> commit: 913ec479bb5cc27f99f24d5fd111b3ef29a4deb9 ("drm/mgag200: Replace VRAM helpers with SHMEM helpers")
>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>>>
>>>
>>> in testcase: vm-scalability
>>> on test machine: 288 threads Intel(R) Xeon Phi(TM) CPU 7295 @ 1.50GHz with 80G memory
>>> with following parameters:
>>>
>>> runtime: 300s
>>> size: 8T
>>> test: anon-cow-seq-hugetlb
>>> cpufreq_governor: performance
>>> ucode: 0x11
>
> Hello Thomas,
>
> Did drm changes really impact anon-cow-seq-hugetlb performance?
>
> My change c0d0381ade79 ("hugetlbfs: use i_mmap_rwsem for more pmd sharing
> synchronization") caused a -33.4% regression of anon-cow-seq-hugetlb. A
> recent change 34ae204f185 (hugetlbfs: remove call to huge_pte_alloc without
> i_mmap_rwsem) was tested by Zhengjun Xing and improved performance by 20
> something percent. That seems in line with this report/improvement.
Some of DRM's memory management might be affected by hugetable changes.
While I cannot really point to a specific location, it's not impossible
that there's a connection.
>
> Perhaps the tooling is not always accurate in determining the commit which
> causes the performance changes?
> Perhaps I am misreading information in the reports?
>
From what I remember, some of these tests print to the console, which
has always been slow, and has generally been a bad idea for performance
tests. I guess these tests are not very accurate.
Best regards
Thomas
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 516 bytes --]
next prev parent reply other threads:[~2020-08-29 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 8:58 kernel test robot
2020-08-27 9:16 ` Thomas Zimmermann
2020-08-27 14:56 ` Mike Kravetz
2020-08-29 18:06 ` Thomas Zimmermann [this message]
2020-08-31 6:11 ` Feng Tang
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=f9664139-e28c-ba8e-b4e4-d505baf9069a@suse.de \
--to=tzimmermann@suse.de \
--cc=John.p.donnelly@oracle.com \
--cc=emil.velikov@collabora.com \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mike.kravetz@oracle.com \
--cc=rong.a.chen@intel.com \
--cc=ying.huang@intel.com \
--cc=zhengjun.xing@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
all inboxes | Powered by JetHome®