Messages in this thread | | | Date | Mon, 14 Aug 2006 08:21:27 -0400 | From | Rik van Riel <> | Subject | Re: [RFC][PATCH 0/4] VM deadlock prevention -v4 |
| |
Evgeniy Polyakov wrote: > On Sun, Aug 13, 2006 at 05:42:47PM -0700, Daniel Phillips (phillips@google.com) wrote:
>> As for sk_buff cow break, we need to look at which network paths do it >> (netfilter obviously, probably others) and decide whether we just want >> to declare that the feature breaks network block IO, or fix the feature >> so it plays well with reserve accounting. > > I would suggest to consider skb cow (cloning) as a must.
That should not be any problem, since skb's (including cowed ones) are short lived anyway. Allocating a little bit more memory is fine when we have a guarantee that the memory will be freed again shortly.
-- What is important? What you want to be true, or what is true? - 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/
| |