From: Nathan Lynch <nathanl@linux•ibm.com>
To: Michael Ellerman <mpe@ellerman•id.au>
Cc: Vaibhav Jain <vaibhav@linux•ibm.com>,
paulus@samba•org, linuxppc-dev@lists•ozlabs.org,
npiggin@gmail•com,
"Aneesh Kumar K.V" <aneesh.kumar@linux•ibm.com>
Subject: Re: ["RFC PATCH" 1/2] powerpc/mm: Fix node look up with numa=off boot
Date: Tue, 09 Jul 2019 09:56:34 -0500 [thread overview]
Message-ID: <875zobs1ct.fsf@linux.ibm.com> (raw)
In-Reply-To: <877e8x3mb4.fsf@concordia.ellerman.id.au>
Michael Ellerman <mpe@ellerman•id.au> writes:
> Nathan Lynch <nathanl@linux•ibm.com> writes:
>> "Aneesh Kumar K.V" <aneesh.kumar@linux•ibm.com> writes:
>>>> Just checking: do people still need numa=off? Seems like it's a
>>>> maintenance burden :-)
>>>>
>>>
>>> That is used in kdump kernel.
>>
>> I see, thanks.
>
> That doesn't mean it's a good idea :)
>
> Does it actually reduce memory usage much? Last time I dug into the
> kdump kernel's usage of weird command line flags none of them really did
> anything useful.
I think it's intended to work around bugs in numa initialization, e.g.
https://www.suse.com/support/kb/doc/?id=7023399
Hopefully the original bug with numa/kdump interaction has been fixed?
prev parent reply other threads:[~2019-07-09 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 8:36 ["RFC PATCH" 1/2] powerpc/mm: Fix node look up with numa=off boot Aneesh Kumar K.V
2019-06-29 8:36 ` ["RFC PATCH" 2/2] powerpc/mm: Conslidate numa_enable check and min_common_depth check Aneesh Kumar K.V
2019-06-29 9:06 ` Aneesh Kumar K.V
2019-06-29 15:39 ` Vaibhav Jain
2019-06-29 15:54 ` Aneesh Kumar K.V
2019-06-29 9:03 ` ["RFC PATCH" 1/2] powerpc/mm: Fix node look up with numa=off boot Aneesh Kumar K.V
2019-07-01 16:42 ` Nathan Lynch
2019-07-02 2:45 ` Aneesh Kumar K.V
2019-07-02 15:57 ` Nathan Lynch
2019-07-04 14:29 ` Michael Ellerman
2019-07-09 14:56 ` Nathan Lynch [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=875zobs1ct.fsf@linux.ibm.com \
--to=nathanl@linux$(echo .)ibm.com \
--cc=aneesh.kumar@linux$(echo .)ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=npiggin@gmail$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=vaibhav@linux$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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