|From:||David Miller <davem-AT-davemloft.net>|
|Subject:||Re: [RFC][PATCH 2/9] deadlock prevention core|
|Date:||Sun, 13 Aug 2006 16:55:40 -0700 (PDT)|
|Cc:||riel-AT-redhat.com, tgraf-AT-suug.ch, a.p.zijlstra-AT-chello.nl, linux-mm-AT-kvack.org, linux-kernel-AT-vger.kernel.org, netdev-AT-vger.kernel.org|
From: Daniel Phillips <firstname.lastname@example.org> Date: Sun, 13 Aug 2006 15:05:25 -0700 > By the way, another way to avoid impact on the normal case is an > experimental option such as CONFIG_PREVENT_NETWORK_BLOCKIO_DEADLOCK. That would just make the solution look more like a hack, and "bolted on" rather than designed. I think there is more profitability from a solution that really does something about "network memory", and doesn't try to say "these devices are special" or "these sockets are special". Special cases generally suck. We already limit and control TCP socket memory globally in the system. If we do this for all socket and anonymous network buffer allocations, which is sort of implicity in Evgeniy's network tree allocator design, we can solve this problem in a more reasonable way. And here's the kick, there are other unrelated highly positive consequences to using Evgeniy's network tree allocator. It doesn't just solve the _one_ problem it was built for, it solves several problems. And that is the hallmark signature of good design. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html
Copyright © 2006, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds