From: Suren Baghdasaryan <surenb@google.com>
To: "T.J. Alumbaugh" <talumbau@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@techsingularity.net>,
linux-mm <linux-mm@kvack.org>
Subject: Re: ptf-threads on mm-unstable seems to regressed from 6.2-rc3
Date: Sun, 22 Jan 2023 15:09:46 -0800 [thread overview]
Message-ID: <CAJuCfpH=V1NY7BTthL9wtSUahxXmOLkJffj1rsNASk_AMYu6RA@mail.gmail.com> (raw)
In-Reply-To: <CABmGT5HsoBv0RpGzFsz_Ja0g_y5wv10JZf9N+iAfcx467MaGHA@mail.gmail.com>
On Sun, Jan 22, 2023 at 10:53 AM T.J. Alumbaugh <talumbau@google.com> wrote:
>
> Hi Suren,
>
> On Sun, Jan 22, 2023 at 12:28 AM Suren Baghdasaryan <surenb@google.com> wrote:
>
> > This is comparing mm-unstable ToT (c04e06325f11 "mm: multi-gen LRU:
> > simplify lru_gen_look_around()") with 6.2-rc3, which was my previous
> > baseline (both are tested without my patchset). Not sure if this is
> > expected, so sending a warning. If this is unexpected, it would also
> > be great if someone can confirm this is not a fluke on my side.
Sorry, false alert. I found the reason for regression is the
CONFIG_KASAN which was enabled in one case and disabled in the other.
>
> I don't believe this is caused by MGLRU, but I think knowing that
> would help bisect the regression. Can you confirm that MGLRU is not
> enabled for those results?
CONFIG_LRU_GEN was not set in both cases.
Sorry for the noise.
Thanks,
Suren.
>
> Thanks,
> -T.J.
prev parent reply other threads:[~2023-01-22 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 7:28 Suren Baghdasaryan
2023-01-22 18:53 ` T.J. Alumbaugh
2023-01-22 23:09 ` Suren Baghdasaryan [this message]
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='CAJuCfpH=V1NY7BTthL9wtSUahxXmOLkJffj1rsNASk_AMYu6RA@mail.gmail.com' \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=talumbau@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox