Jeff Dike wrote: > Yeah, it's a bit non-obvious what 0 means in the twisty little maze of > GFP_ flags. > > However, I do want to push the system into reclaim later. It looks > like the only difference between 0 and GFP_ATOMIC is the use of > emergency pools, which I don't really want to exercise anyway. > > ...This look OK to you?... > > + /* 0 means don't wait (like GFP_ATOMIC) and > + * don't dip into emergency pools (unlike > + * GFP_ATOMIC). > + */ > + new = kmalloc(sizeof(*new), 0);
If you have a believable use for gfp_mask=0 then why not add GFP_NOWAIT or some such to gfp.h? Regards, Daniel ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ User-mode-linux-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
