From: Dave Hansen <dave.hansen@intel.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RFC] x86/mm/pat: Restore large pages after fragmentation
Date: Thu, 16 Apr 2020 15:38:38 -0700 [thread overview]
Message-ID: <fb793919-df5d-42cc-6b2e-d387e0faa42e@intel.com> (raw)
In-Reply-To: <20200416221238.qrkaajbe3m6ca2h2@box>
On 4/16/20 3:12 PM, Kirill A. Shutemov wrote:
> We already have it in kernel: CONFIG_CPA_DEBUG. It messes up with the
> mapping every 30 seconds. It is pretty good for the change too. It
> produces a lot of 2M/1G pages to be restored. I run it over night in my
> setup and it survives.
That's good for stability, and thanks for running it! (and please add
that nugget to the changelog)
It's good that you see it restoring some mappings, but, does it restore
*all* the 1G/2M pages that it started with (minus the ones that were
fractured for other reasons)? That should be pretty easy to check for.
next prev parent reply other threads:[~2020-04-16 22:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 21:32 Kirill A. Shutemov
2020-04-16 22:03 ` Dave Hansen
2020-04-16 22:12 ` Kirill A. Shutemov
2020-04-16 22:38 ` Dave Hansen [this message]
2020-04-17 0:52 ` Mika Penttilä
2020-04-17 11:42 ` Kirill A. Shutemov
2020-04-17 12:05 ` Mika Penttilä
2020-04-17 12:18 ` Peter Zijlstra
2020-04-17 14:42 ` Kirill A. Shutemov
2020-04-17 15:17 ` Peter Zijlstra
2020-04-17 15:47 ` Peter Zijlstra
2020-04-17 16:54 ` Kirill A. Shutemov
2020-04-25 11:43 ` [x86/mm/pat] ae64ac1a83: BUG:Bad_page_state_in_process kernel test robot
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=fb793919-df5d-42cc-6b2e-d387e0faa42e@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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