From: Ben Hutchings <ben@decadent.org.uk>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] mm: Try harder to allocate vmemmap blocks
Date: Fri, 15 Feb 2013 01:47:56 +0000 [thread overview]
Message-ID: <1360892876.5374.332.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <20130214064048.GB8372@cmpxchg.org>
[-- Attachment #1: Type: text/plain, Size: 2387 bytes --]
On Thu, 2013-02-14 at 01:40 -0500, Johannes Weiner wrote:
> On Thu, Feb 14, 2013 at 04:34:28AM +0000, Ben Hutchings wrote:
> > Hot-adding memory on x86_64 normally requires huge page allocation.
> > When this is done to a VM guest, it's usually because the system is
> > already tight on memory, so the request tends to fail. Try to avoid
> > this by adding __GFP_REPEAT to the allocation flags.
> >
> > Reported-and-tested-by: Bernhard Schmidt <Bernhard.Schmidt@lrz.de>
> > Reference: http://bugs.debian.org/699913
> > Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
>
> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
>
> > We could go even further and use __GFP_NOFAIL, but I'm not sure
> > whether that would be a good idea.
>
> If __GFP_REPEAT is not enough, I'd rather fall back to regular page
> backing at this point:
Oh yes, I had considered doing that before settling on __GFP_REPEAT. It
does seem worth doing. Perhaps you could also log a specific warning,
as the use of 4K page entries for this could have a significant
performance impact.
Ben.
> diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
> index 2ead3c8..1f5301d 100644
> --- a/arch/x86/mm/init_64.c
> +++ b/arch/x86/mm/init_64.c
> @@ -919,6 +919,7 @@ vmemmap_populate(struct page *start_page, unsigned long size, int node)
> {
> unsigned long addr = (unsigned long)start_page;
> unsigned long end = (unsigned long)(start_page + size);
> + int use_huge = cpu_has_pse;
> unsigned long next;
> pgd_t *pgd;
> pud_t *pud;
> @@ -934,8 +935,8 @@ vmemmap_populate(struct page *start_page, unsigned long size, int node)
> pud = vmemmap_pud_populate(pgd, addr, node);
> if (!pud)
> return -ENOMEM;
> -
> - if (!cpu_has_pse) {
> +retry_pmd:
> + if (!use_huge) {
> next = (addr + PAGE_SIZE) & PAGE_MASK;
> pmd = vmemmap_pmd_populate(pud, addr, node);
>
> @@ -957,8 +958,10 @@ vmemmap_populate(struct page *start_page, unsigned long size, int node)
> pte_t entry;
>
> p = vmemmap_alloc_block_buf(PMD_SIZE, node);
> - if (!p)
> - return -ENOMEM;
> + if (!p) {
> + use_huge = 0;
> + goto retry_pmd;
> + }
>
> entry = pfn_pte(__pa(p) >> PAGE_SHIFT,
> PAGE_KERNEL_LARGE);
>
--
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-02-15 1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 4:34 Ben Hutchings
2013-02-14 6:40 ` Johannes Weiner
2013-02-15 1:47 ` Ben Hutchings [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=1360892876.5374.332.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.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