[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wh2_yEuAC5=9VWefK+0JD9pAKf8qL-vpSmS7MtLA8SZEA@mail.gmail.com>
Date: Mon, 20 Sep 2021 16:29:52 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Minchan Kim <minchan@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Laura Abbott <labbott@...nel.org>,
Oliver Sang <oliver.sang@...el.com>,
David Hildenbrand <david@...hat.com>,
John Dias <joaodias@...gle.com>,
Matthew Wilcox <willy@...radead.org>,
Michal Hocko <mhocko@...e.com>,
Suren Baghdasaryan <surenb@...gle.com>,
Vlastimil Babka <vbabka@...e.cz>,
LKML <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>, lkp@...ts.01.org,
kernel test robot <lkp@...el.com>,
"Huang, Ying" <ying.huang@...el.com>,
Feng Tang <feng.tang@...el.com>, zhengjun.xing@...el.com,
Chris Goldsworthy <cgoldswo@...eaurora.org>
Subject: Re: [PATCH v3] mm: fs: invalidate bh_lrus for only cold path
On Tue, Sep 7, 2021 at 2:24 PM Minchan Kim <minchan@...nel.org> wrote:
>
> kernel test robot reported the regression of fio.write_iops[1]
> with [2].
>
> Since lru_add_drain is called frequently, invalidate bh_lrus
> there could increase bh_lrus cache miss ratio, which needs
> more IO in the end.
>
> This patch moves the bh_lrus invalidation from the hot path(
> e.g., zap_page_range, pagevec_release) to cold path(i.e.,
> lru_add_drain_all, lru_cache_disable).
Was this confirmed to fix the regression?
I only see the "tested with 5.14" that the regression was still there
https://lore.kernel.org/lkml/034fc860-d0d0-0c61-09d2-3c41c4f020c6@intel.com/
I don't see a confirmation that this patch fixed it.
It looks likely, but if you have the confirmation somewhere, it would
help to link that too.
Or did I miss it?
Linus
Powered by blists - more mailing lists