public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>
Cc: "Liang, Liang (Leo)" <Liang.Liang@amd.com>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>,
	linux-kernel@vger.kernel.org,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Huang, Ray" <Ray.Huang@amd.com>,
	"Koenig, Christian" <Christian.Koenig@amd.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	George Kennedy <george.kennedy@oracle.com>
Subject: Re: slow boot with 7fef431be9c9 ("mm/page_alloc: place pages to tail in __free_pages_core()")
Date: Sat, 13 Mar 2021 15:48:11 +0200	[thread overview]
Message-ID: <YEzCm/Uwvw7kKpd7@linux.ibm.com> (raw)
In-Reply-To: <0AE49D98-171A-42B9-9CFC-9193A9BD3346@redhat.com>

Hi,

On Sat, Mar 13, 2021 at 10:05:23AM +0100, David Hildenbrand wrote:
> > Am 13.03.2021 um 05:04 schrieb Liang, Liang (Leo) <Liang.Liang@amd.com>:
> > 
> > Hi David,
> > 
> > Which benchmark tool you prefer? Memtest86+ or else?
> 
> Hi Leo,
> 
> I think you want something that runs under Linux natively.
> 
> I‘m planning on coding up a kernel module to walk all 4MB pages in the
> freelists and perform a stream benchmark individually. Then we might be
> able to identify the problematic range - if there is a problematic range :)

My wild guess would be that the pages that are now at the head of free
lists have wrong caching enabled. Might be worth checking in your test
module.

> Guess I‘ll have it running by Monday and let you know.
> 
> Cheers!

-- 
Sincerely yours,
Mike.

  reply	other threads:[~2021-03-13 13:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 14:41 slow boot with 7fef431be9c9 ("mm/page_alloc: place pages to tail in __free_pages_core()") Deucher, Alexander
2021-03-11 15:02 ` David Hildenbrand
2021-03-12 14:06   ` Deucher, Alexander
2021-03-12 14:12     ` David Hildenbrand
2021-03-12 15:39       ` Deucher, Alexander
2021-03-12 15:48         ` David Hildenbrand
2021-03-12 16:15           ` Deucher, Alexander
2021-03-12 16:19         ` Liang, Liang (Leo)
2021-03-12 16:46           ` David Hildenbrand
2021-03-13  4:04             ` Liang, Liang (Leo)
2021-03-13  9:05               ` David Hildenbrand
2021-03-13 13:48                 ` Mike Rapoport [this message]
2021-03-15 13:04                   ` David Hildenbrand
2021-03-16  0:36                     ` Liang, Liang (Leo)
2021-03-16  6:50                       ` Mike Rapoport
2021-03-16  8:00                         ` Liang, Liang (Leo)
2021-03-16  8:37                           ` David Hildenbrand
2021-03-16  8:43                             ` Liang, Liang (Leo)
2021-03-16  8:54                               ` David Hildenbrand
2021-03-16  8:58                                 ` Liang, Liang (Leo)
2021-03-16  9:08                                   ` David Hildenbrand
2021-03-16 10:30                                     ` Mike Rapoport
2021-03-16 11:02                                       ` Liang, Liang (Leo)
2021-03-16 11:10                                         ` David Hildenbrand

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=YEzCm/Uwvw7kKpd7@linux.ibm.com \
    --to=rppt@linux.ibm.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=Liang.Liang@amd.com \
    --cc=Ray.Huang@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=david@redhat.com \
    --cc=george.kennedy@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox