[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a815a022-cf3e-fe4b-ee23-191523ed1980@linux.ibm.com>
Date: Mon, 14 Jun 2021 21:38:44 +0530
From: "Aneesh Kumar K.V" <aneesh.kumar@...ux.ibm.com>
To: kernel test robot <oliver.sang@...el.com>
Cc: 0day robot <lkp@...el.com>, LKML <linux-kernel@...r.kernel.org>,
lkp@...ts.01.org, ying.huang@...el.com, feng.tang@...el.com,
zhengjun.xing@...ux.intel.com, linux-mm@...ck.org,
akpm@...ux-foundation.org, mpe@...erman.id.au,
linuxppc-dev@...ts.ozlabs.org, kaleshsingh@...gle.com,
npiggin@...il.com, joel@...lfernandes.org,
Christophe Leroy <christophe.leroy@...roup.eu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Kirill A . Shutemov" <kirill@...temov.name>
Subject: Re: [mm/mremap] ecf8443e51: vm-scalability.throughput -29.4%
regression
On 6/14/21 8:25 PM, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed a -29.4% regression of vm-scalability.throughput due to commit:
>
>
> commit: ecf8443e51a862b261313c2319ab4e4aed9e6b7e ("[PATCH v7 02/11] mm/mremap: Fix race between MOVE_PUD mremap and pageout")
> url: https://github.com/0day-ci/linux/commits/Aneesh-Kumar-K-V/Speedup-mremap-on-ppc64/20210607-135424
> base: https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git next
>
>
We dropped that approach and is now using
https://lore.kernel.org/linux-mm/20210610083549.386085-1-aneesh.kumar@linux.ibm.com
Instead of pud lock we are now using rmap lock with mremap.
Can you check with that series?
-aneesh
Powered by blists - more mailing lists