On Thu 20-12-18 20:26:28, Pingfan Liu wrote:
> On Thu, Dec 20, 2018 at 7:35 PM Michal Hocko <mhocko@xxxxxxxxxx> wrote:
> >
> > On Thu 20-12-18 17:50:38, Pingfan Liu wrote:
> > [...]
> > > @@ -453,7 +456,12 @@ static inline int gfp_zonelist(gfp_t flags)
> > > */
> > > static inline struct zonelist *node_zonelist(int nid, gfp_t flags)
> > > {
> > > - return NODE_DATA(nid)->node_zonelists + gfp_zonelist(flags);
> > > + if (unlikely(!possible_zonelists[nid])) {
> > > + WARN_ONCE(1, "alloc from offline node: %d\n", nid);
> > > + if (unlikely(build_fallback_zonelists(nid)))
> > > + nid = first_online_node;
> > > + }
> > > + return possible_zonelists[nid] + gfp_zonelist(flags);
> > > }
> >
> > No, please don't do this. We do not want to make things work magically
>
> For magically, if you mean directly replies on zonelist instead of on
> pgdat struct, then it is easy to change
No, I mean that we _know_ which nodes are possible. Platform is supposed
to tell us. We should just do the intialization properly. What we do now
instead is a pile of hacks that fit magically together. And that should
be changed.
> > and we definitely do not want to put something like that into the hot
>
> But the cose of "unlikely" can be ignored, why can it not be placed
> in the path?
unlikely will simply put the code outside of the hot path. The condition
is still there. There are people desperately fighting to get every
single cycle out of the page allocator. Now you want them to pay a
branch which is relevant only for few obscure HW setups.
> > path. We definitely need zonelists to be build transparently for all
> > possible nodes during the init time.
>
> That is the point, whether the all nodes should be instanced at boot
> time, or not be instanced until there is requirement.
And that should be done at init time. We have all the information
necessary at that time.
--
Michal Hocko
SUSE Labs
