Re: [PATCH 1/2] x86, numa: always initialize all possible nodes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Barret Rhoden <brho@xxxxxxxxxx>
- Subject: Re: [PATCH 1/2] x86, numa: always initialize all possible nodes
- From: Michal Hocko <mhocko@xxxxxxxxxx>
- Date: Wed, 26 Jun 2019 15:54:50 +0200
- Cc: linux-mm@xxxxxxxxx, Pingfan Liu <kernelfans@xxxxxxxxx>, Dave Hansen <dave.hansen@xxxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, x86@xxxxxxxxxx, Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>, Michael Ellerman <mpe@xxxxxxxxxxxxxx>, Tony Luck <tony.luck@xxxxxxxxx>, linuxppc-dev@xxxxxxxxxxxxxxxx, linux-ia64@xxxxxxxxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>
- In-reply-to: <20190502130031.GC29835@dhcp22.suse.cz>
- References: <20190212095343.23315-1-mhocko@kernel.org> <20190212095343.23315-2-mhocko@kernel.org> <34f96661-41c2-27cc-422d-5a7aab526f87@google.com> <20190502130031.GC29835@dhcp22.suse.cz>
- User-agent: Mutt/1.10.1 (2018-07-13)
On Thu 02-05-19 09:00:31, Michal Hocko wrote:
> On Wed 01-05-19 15:12:32, Barret Rhoden wrote:
> [...]
> > A more elegant solution may be to avoid registering with sysfs during early
> > boot, or something else entirely. But I figured I'd ask for help at this
> > point. =)
>
> Thanks for the report and an excellent analysis! This is really helpful.
> I will think about this some more but I am traveling this week. It seems
> really awkward to register a sysfs file for an empty range. That looks
> like a bug to me.
I am sorry, but I didn't get to this for a long time and I am still
busy. The patch has been dropped from the mm tree (thus linux-next). I
hope I can revisit this or somebody else will take over and finish this
work. This is much more trickier than I anticipated unfortunately.
--
Michal Hocko
SUSE Labs
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]