Re: [PATCH 1/1] network memory allocator.

On Mon, Aug 14, 2006 at 10:07:48PM +1000, Keith Owens (kaos@ocs.com.au) wrote:

Evgeniy Polyakov (on Mon, 14 Aug 2006 15:04:03 +0400) wrote:

quoted

Network tree allocator can be used to allocate memory for all network
operations from any context....
...
Design of allocator allows to map all node's pages into userspace thus
allows to have true zero-copy support for both sending and receiving
dataflows.

Is that true for architectures with virtually indexed caches?  How do
you avoid the cache aliasing problems?

Pages are preallocated and stolen from main memory allocator, what is
the problem with that caches? Userspace can provide enough offset so
that pages would not create aliases - it is usuall mmap.

-- 
	Evgeniy Polyakov