All of lore.kernel.org
 help / color / mirror / Atom feed
From: Victor Aoqui <victora@linux.vnet.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	mpe@ellerman.id.au, khandual@linux.vnet.ibm.com,
	victora@br.ibm.com, mauricfo@linux.vnet.ibm.com
Subject: Re: [PATCH v3] powerpc/mm: Implemented default_hugepagesz verification for powerpc
Date: Mon, 14 Aug 2017 19:06:31 -0300	[thread overview]
Message-ID: <5c722efebd21bcd56c2a857154bb1830@linux.vnet.ibm.com> (raw)
In-Reply-To: <87zibf3mfg.fsf@linux.vnet.ibm.com>

Em 2017-08-04 02:57, Aneesh Kumar K.V escreveu:
> Victor Aoqui <victora@linux.vnet.ibm.com> writes:
> 
>> Implemented default hugepage size verification (default_hugepagesz=)
>> in order to allow allocation of defined number of pages (hugepages=)
>> only for supported hugepage sizes.
>> 
>> Signed-off-by: Victor Aoqui <victora@linux.vnet.ibm.com>
> 
> I am still not sure about this. With current upstream we get
> 
>  PCI: Probing PCI hardware
>  PCI: Probing PCI hardware done
> 
> 
>  HugeTLB: unsupported default_hugepagesz 2097152. Reverting to
> 16777216
> 
>  HugeTLB registered 16.0 MiB page size, pre-allocated 0 pages
> 
> 
>  HugeTLB registered 16.0 GiB page size, pre-allocated 0 pages
> 
> That warning is added by
> 
> d715cf804a0318e83c75c0a7abd1a4b9ce13e8da
> 
> Which should be good enough right ?
> 
> -aneesh

Hi Aneesh,

Sorry for the delay. I was on vacation.
Yes, that solves the issue. This patch was accepted when I was fixing 
the last version.
Sorry for the inconvenience.

-- 
Victor Aoqui

  reply	other threads:[~2017-08-14 22:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 23:52 [PATCH v3] powerpc/mm: Implemented default_hugepagesz verification for powerpc Victor Aoqui
2017-08-04  5:57 ` Aneesh Kumar K.V
2017-08-14 22:06   ` Victor Aoqui [this message]
2017-08-04 18:17 ` Mike Kravetz
2017-08-14 22:12   ` Victor Aoqui

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=5c722efebd21bcd56c2a857154bb1830@linux.vnet.ibm.com \
    --to=victora@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mauricfo@linux.vnet.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=victora@br.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.