From: Mike Kravetz <mike.kravetz@oracle.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Michal Hocko <mhocko@kernel.org>, Hugh Dickins <hughd@google.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.vnet.ibm.com>,
Andrea Arcangeli <aarcange@redhat.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Prakash Sangappa <prakash.sangappa@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
stable@vger.kernel.org, lkp@01.org
Subject: Re: [LKP] [hugetlbfs] 9c83282117: vm-scalability.throughput -4.3% regression
Date: Wed, 2 Jan 2019 08:54:07 -0800 [thread overview]
Message-ID: <21117eab-862e-562b-0c86-ec2ccc1f68e4@oracle.com> (raw)
In-Reply-To: <20181228142608.GA17624@shao2-debian>
On 12/28/18 6:26 AM, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a -4.3% regression of vm-scalability.throughput due to commit:
>
>
> commit: 9c83282117778856d647ffc461c4aede2abb6742 ("[PATCH v3 1/2] hugetlbfs: use i_mmap_rwsem for more pmd sharing synchronization")
> url: https://github.com/0day-ci/linux/commits/Mike-Kravetz/hugetlbfs-use-i_mmap_rwsem-for-better-synchronization/20181223-095226
>
>
> in testcase: vm-scalability
> on test machine: 104 threads Intel(R) Xeon(R) Platinum 8170 CPU @ 2.10GHz with 64G memory
> with following parameters:
>
> runtime: 300s
> size: 8T
> test: anon-cow-seq-hugetlb
> cpufreq_governor: performance
> ucode: 0x200004d
I'll take a closer look.
The patch does introduce longer i_mmap_rwsem hold times for the sake of
correctness. Need to more fully understand the test and results to determine
if this is expected.
--
Mike Kravetz
WARNING: multiple messages have this Message-ID (diff)
From: Mike Kravetz <mike.kravetz@oracle.com>
To: lkp@lists.01.org
Subject: Re: [hugetlbfs] 9c83282117: vm-scalability.throughput -4.3% regression
Date: Wed, 02 Jan 2019 08:54:07 -0800 [thread overview]
Message-ID: <21117eab-862e-562b-0c86-ec2ccc1f68e4@oracle.com> (raw)
In-Reply-To: <20181228142608.GA17624@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On 12/28/18 6:26 AM, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a -4.3% regression of vm-scalability.throughput due to commit:
>
>
> commit: 9c83282117778856d647ffc461c4aede2abb6742 ("[PATCH v3 1/2] hugetlbfs: use i_mmap_rwsem for more pmd sharing synchronization")
> url: https://github.com/0day-ci/linux/commits/Mike-Kravetz/hugetlbfs-use-i_mmap_rwsem-for-better-synchronization/20181223-095226
>
>
> in testcase: vm-scalability
> on test machine: 104 threads Intel(R) Xeon(R) Platinum 8170 CPU @ 2.10GHz with 64G memory
> with following parameters:
>
> runtime: 300s
> size: 8T
> test: anon-cow-seq-hugetlb
> cpufreq_governor: performance
> ucode: 0x200004d
I'll take a closer look.
The patch does introduce longer i_mmap_rwsem hold times for the sake of
correctness. Need to more fully understand the test and results to determine
if this is expected.
--
Mike Kravetz
next prev parent reply other threads:[~2019-01-02 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-22 22:30 [PATCH v3 0/2] hugetlbfs: use i_mmap_rwsem for better synchronization Mike Kravetz
2018-12-22 22:30 ` [PATCH v3 1/2] hugetlbfs: use i_mmap_rwsem for more pmd sharing synchronization Mike Kravetz
2018-12-28 14:26 ` [LKP] [hugetlbfs] 9c83282117: vm-scalability.throughput -4.3% regression kernel test robot
2018-12-28 14:26 ` kernel test robot
2018-12-28 14:26 ` [LKP] " kernel test robot
2019-01-02 16:54 ` Mike Kravetz [this message]
2019-01-02 16:54 ` Mike Kravetz
2018-12-22 22:30 ` [PATCH v3 2/2] hugetlbfs: Use i_mmap_rwsem to fix page fault/truncate race Mike Kravetz
2018-12-24 10:13 ` [PATCH v3 0/2] hugetlbfs: use i_mmap_rwsem for better synchronization Kirill A. Shutemov
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=21117eab-862e-562b-0c86-ec2ccc1f68e4@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dave@stgolabs.net \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@01.org \
--cc=mhocko@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=prakash.sangappa@oracle.com \
--cc=rong.a.chen@intel.com \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.