Messages in this thread |  | | From | Rusty Russell <> | Subject | Re: the new VMt | Date | Wed, 27 Sep 2000 18:14:12 +1100 |
| |
In message <Pine.LNX.4.10.10009250931570.1739-100000@penguin.transmeta.com> you write: > I suspect that the proper way to do this is to just make another gfp_flag, > which is basically another hint to the mm layer that we're doing a multi- > page allocation and that the MM layer should not try forever to handle it. > > In fact, that's independent of whether it is a multi-page allocation or > not. It might be something like __GFP_SOFT - you could use it with single > pages too.
That'd be a lovely interface, now wouldn't it?
*yecch*
Please consider at least:
/* Never fails. */ #define trivial_kmalloc(s) \ ((void)((s) > PAGE_SIZE ? bad_size_##s : __kmalloc((s), GFP_KERNEL)))
/* Can fail */ #define kmalloc(s, pri) __kmalloc((s), (pri)|__GFP_SOFT)
Rusty. -- Hacking time. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |