[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOUHufYdGbgnqNprKVUH8woMR_R5Wcc=281vcmm3+NRO-=+-jw@mail.gmail.com>
Date: Wed, 10 Jul 2024 00:22:40 -0600
From: Yu Zhao <yuzhao@...gle.com>
To: kernel test robot <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com,
Linux Memory Management List <linux-mm@...ck.org>, Andrew Morton <akpm@...ux-foundation.org>,
Muchun Song <muchun.song@...ux.dev>, David Hildenbrand <david@...hat.com>,
Frank van der Linden <fvdl@...gle.com>, Matthew Wilcox <willy@...radead.org>, Peter Xu <peterx@...hat.com>,
Yang Shi <yang@...amperecomputing.com>, linux-kernel@...r.kernel.org,
ying.huang@...el.com, feng.tang@...el.com, fengwei.yin@...el.com
Subject: Re: [linux-next:master] [mm/hugetlb_vmemmap] 875fa64577:
vm-scalability.throughput -34.3% regression
On Mon, Jul 8, 2024 at 11:11 PM kernel test robot <oliver.sang@...el.com> wrote:
>
> Hello,
>
> kernel test robot noticed a -34.3% regression of vm-scalability.throughput on:
>
>
> commit: 875fa64577da9bc8e9963ee14fef8433f20653e7 ("mm/hugetlb_vmemmap: fix race with speculative PFN walkers")
This is likely caused by synchronize_rcu() wandering into the
allocation path. I'll patch that up soon.
Powered by blists - more mailing lists