Received: with ECARTIS (v1.0.0; list netdev); Tue, 29 Apr 2003 04:55:16 -0700 (PDT)
Received: from verein.lst.de (verein.lst.de [212.34.181.86])
	by oss.sgi.com (8.12.9/8.12.9) with SMTP id h3TBt8Fu030401
	for <netdev@oss.sgi.com>; Tue, 29 Apr 2003 04:55:09 -0700
Received: (from hch@localhost)
	by verein.lst.de (8.11.6/8.11.6) id h3TBt6Z22434;
	Tue, 29 Apr 2003 13:55:06 +0200
Date: Tue, 29 Apr 2003 13:55:06 +0200
From: Christoph Hellwig <hch@lst.de>
To: davem@redhat.com
Cc: netdev@oss.sgi.com
Subject: purpose of the skb head pool
Message-ID: <20030429135506.A22411@lst.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
X-archive-position: 2346
X-ecartis-version: Ecartis v1.0.0
Sender: netdev-bounce@oss.sgi.com
Errors-to: netdev-bounce@oss.sgi.com
X-original-sender: hch@lst.de
Precedence: bulk
X-list: netdev

[sorry, wrong Cc: the first time]

net/core/skbuf.c has a small per-cpu pool to keep some hot skbufs around
instead of returning them to the system allocator.  But if you loook
at the slab allocator we'll have exactly that same code duplicated in
there (see functions ac_data, __cache_alloc and kmem_cache_alloc in
slab.c).  So is there some other reason why this pool is needed?