Date: Tue, 08 Aug 2006 18:38:08 -0700 (PDT)
Message-Id: <20060808.183808.74747814.davem@davemloft.net>
To: phillips@google.com
Cc: shemminger@osdl.org, a.p.zijlstra@chello.nl, linux-mm@kvack.org,
       linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC][PATCH 2/9] deadlock prevention core
From: David Miller <davem@davemloft.net>
In-Reply-To: <44D93B60.7030507@google.com>
References: <20060808193345.1396.16773.sendpatchset@lappy>
	<20060808135721.5af713fb@localhost.localdomain>
	<44D93B60.7030507@google.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 762
Lines: 16

From: Daniel Phillips <phillips@google.com>
Date: Tue, 08 Aug 2006 18:33:20 -0700

> Minor rant: the whole skb_alloc familly has degenerated into an unholy
> mess and could use some rethinking.  I believe the current patch gets as
> far as three _'s at the beginning of a function, this shows it is high
> time to reroll the api.

I think it is merely an expression of how dynamic are the operations
that people want to perform on SKBs, and how important it is for
performance to implement COW semantics for the data.
-
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/