Messages in this thread | | | Date | Thu, 10 Aug 2006 22:37:00 -0400 | From | Rik van Riel <> | Subject | Re: [RFC][PATCH 2/9] deadlock prevention core |
| |
Thomas Graf wrote:
> skb->dev is not guaranteed to still point to the "allocating" device > once the skb is freed again so reserve/unreserve isn't symmetric. > You'd need skb->alloc_dev or something.
There's another consequence of this property of the network stack.
Every network interface must be able to fall back to these MEMALLOC allocations, because the memory critical socket could be on another network interface. Hence, we cannot know which network interfaces should (not) be marked MEMALLOC.
-- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan - 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/
| |