> > > So, I don't believe the issue is related > > to setting __GFP_DIRECT_RECLAIM; rather, it stems from the flawed > > design of __GFP_NOFAIL itself. > > Care to elaborate? I've read the documentation explaining why the busy loop is embedded within the page allocation process instead of letting users implement it based on their needs. However, the complexity and numerous issues suggest that this design might be fundamentally flawed. -- Regards Yafang
