Re: [PATCH 1/1] network memory allocator.
From: Evgeniy Polyakov
Date: Mon Aug 14 2006 - 08:18:53 EST
On Mon, Aug 14, 2006 at 10:07:48PM +1000, Keith Owens (kaos@xxxxxxxxxx) wrote:
> Evgeniy Polyakov (on Mon, 14 Aug 2006 15:04:03 +0400) wrote:
> >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
> 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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/