All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xing Zhengjun <zhengjun.xing@linux.intel.com>
To: Mike Kravetz <mike.kravetz@oracle.com>,
	kernel test robot <rong.a.chen@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.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>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org
Subject: Re: [LKP] Re: [hugetlbfs] c0d0381ade: vm-scalability.throughput -33.4% regression
Date: Tue, 13 Oct 2020 14:05:31 +0800	[thread overview]
Message-ID: <6922f83b-32af-0535-c251-5bf2711a0e30@linux.intel.com> (raw)
In-Reply-To: <a44417ad-ad5c-aab6-d656-badd4cfad60e@oracle.com>



On 10/13/2020 11:01 AM, Mike Kravetz wrote:
> On 10/12/20 6:59 PM, Xing Zhengjun wrote:
>>
>>
>> On 10/13/2020 1:40 AM, Mike Kravetz wrote:
>>> On 10/11/20 10:29 PM, Xing Zhengjun wrote:
>>>> Hi Mike,
>>>>
>>>>      I re-test it in v5.9-rc8, the regression still existed. It is almost the same as 34ae204f1851. Do you have time to look at it? Thanks.
>>>>
>>>
>>> Thank you for testing.
>>>
>>> Just curious, did you apply the series in this thread or just test v5.9-rc8?
>>> If just testing v5.9-rc8, no changes to this code were added after 34ae204f1851,
>>> so results being the same are expected.
>>>
>>
>> I just test v5.9-rc8. Where can I find the series patches you mentioned here? Or just wait for the next mainline release?
>>
> 
> My apologies.  I missed that you were not cc'ed on this thred:
> https://lore.kernel.org/linux-mm/20200706202615.32111-1-mike.kravetz@oracle.com/
> 
> As mentioned, there will likely be another revision to the way locking is
> handled.  The new scheme will try to consider performance as is done in
> the above link.  I suggest you wait for next revision.  If you do not mind,
> I will cc you when the new code is posted.
> 

OK. I will wait for the next revision.

-- 
Zhengjun Xing

  reply	other threads:[~2020-10-13  6:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  0:55 [hugetlbfs] c0d0381ade: vm-scalability.throughput -33.4% regression kernel test robot
2020-06-22  0:55 ` kernel test robot
2020-06-22 22:01 ` Mike Kravetz
2020-06-22 22:01   ` Mike Kravetz
2020-06-25 21:33   ` Mike Kravetz
2020-06-25 21:33     ` Mike Kravetz
2020-08-21  8:39     ` [LKP] " Xing Zhengjun
2020-08-21  8:39       ` Xing Zhengjun
2020-08-21 21:02       ` [LKP] " Mike Kravetz
2020-08-21 21:02         ` Mike Kravetz
2020-08-21 23:36         ` [LKP] " Mike Kravetz
2020-08-21 23:36           ` Mike Kravetz
2020-10-12  5:29           ` [LKP] " Xing Zhengjun
2020-10-12 17:40             ` Mike Kravetz
2020-10-13  1:59               ` Xing Zhengjun
2020-10-13  3:01                 ` Mike Kravetz
2020-10-13  6:05                   ` Xing Zhengjun [this message]
2020-07-06 20:26 ` [RFC PATCH 0/3] hugetlbfs: address fault time regression Mike Kravetz
2020-07-06 20:26   ` [RFC PATCH 1/3] Revert: "hugetlbfs: Use i_mmap_rwsem to address page fault/truncate race" Mike Kravetz
2020-07-06 20:26   ` [RFC PATCH 2/3] hugetlbfs: Only take i_mmap_rwsem when sharing is possible Mike Kravetz
2020-07-21  0:56     ` [hugetlbfs] 878308e2e0: vm-scalability.throughput 1.2% improvement kernel test robot
2020-07-06 20:26   ` [RFC PATCH 3/3] huegtlbfs: handle page fault/truncate races Mike Kravetz

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=6922f83b-32af-0535-c251-5bf2711a0e30@linux.intel.com \
    --to=zhengjun.xing@linux.intel.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=lkp@lists.01.org \
    --cc=mhocko@kernel.org \
    --cc=mike.kravetz@oracle.com \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=prakash.sangappa@oracle.com \
    --cc=rong.a.chen@intel.com \
    --cc=torvalds@linux-foundation.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.