Actually, at this point we _know_ page->list.{prev,next} are
NULL.
We can use this to add the pages to a special list, from where
__alloc_pages() and kswapd can move them to the free list, in
process context.
I don't think there should be any special logic on how to free a page
outside of the page allocator itself. Certainly this kind of stuff
doesn't belong in the networking.
Pages can be freed from arbitrary contexts, and the page allocator
should be the part the knows how to deal with it.
Maybe I don't understand and you're really suggesting something else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/