From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Keith Owens <kaos@ocs.com.au>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 1/1] network memory allocator.
Date: Mon, 14 Aug 2006 16:20:50 +0400 [thread overview]
Message-ID: <20060814122049.GC18321@2ka.mipt.ru> (raw)
In-Reply-To: <9286.1155557268@ocs10w.ocs.com.au>
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:
> >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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-08-14 12:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 11:04 Evgeniy Polyakov
2006-08-14 11:22 ` David Miller, Evgeniy Polyakov
2006-08-14 11:32 ` Evgeniy Polyakov
2006-08-14 11:40 ` Andi Kleen
2006-08-14 11:46 ` Evgeniy Polyakov
2006-08-14 12:07 ` Keith Owens
2006-08-14 12:20 ` Evgeniy Polyakov [this message]
2006-08-14 17:42 ` Rick Jones
2006-08-14 20:15 ` David Miller, Rick Jones
2006-08-14 12:25 ` Peter Zijlstra
2006-08-14 12:35 ` Evgeniy Polyakov
2006-08-14 12:38 ` Evgeniy Polyakov
2006-08-15 10:55 ` Peter Zijlstra
2006-08-15 11:26 ` Evgeniy Polyakov
2006-08-15 12:03 ` Peter Zijlstra
2006-08-15 12:34 ` Evgeniy Polyakov
2006-08-15 13:49 ` Peter Zijlstra
2006-08-15 14:15 ` Evgeniy Polyakov
2006-08-15 14:48 ` Peter Zijlstra
2006-08-15 15:05 ` Evgeniy Polyakov
2006-08-15 15:07 ` Evgeniy Polyakov
2006-08-15 17:42 ` Peter Zijlstra
2006-08-15 17:49 ` Evgeniy Polyakov
2006-08-16 2:52 ` Bill Fink
2006-08-16 5:38 ` Evgeniy Polyakov
2006-08-14 17:46 ` Rick Jones
2006-08-14 19:42 ` Evgeniy Polyakov
2006-08-15 7:27 ` Andrew Morton
2006-08-15 8:08 ` Andi Kleen
2006-08-15 10:02 ` Evgeniy Polyakov
2006-08-15 10:27 ` David Miller, Evgeniy Polyakov
2006-08-15 9:20 ` Evgeniy Polyakov
2006-08-15 20:21 ` Arnd Bergmann
2006-08-16 5:35 ` Evgeniy Polyakov
2006-08-16 8:48 ` Christoph Hellwig
2006-08-16 9:00 ` Evgeniy Polyakov
2006-08-16 9:05 ` David Miller, Evgeniy Polyakov
2006-08-16 9:10 ` Christoph Hellwig
2006-08-16 9:32 ` Evgeniy Polyakov
2006-08-16 9:38 ` Christoph Hellwig
2006-08-16 9:40 ` David Miller, Christoph Hellwig
2006-08-16 9:44 ` Christoph Hellwig
2006-08-16 9:42 ` Christoph Hellwig
2006-08-16 11:27 ` Arnd Bergmann
2006-08-16 12:00 ` Evgeniy Polyakov
2006-08-16 12:25 ` Andi Kleen
2006-08-18 2:25 ` Christoph Lameter
2006-08-18 9:29 ` Andi Kleen
2006-08-18 8:51 ` David Miller, Andi Kleen
2006-08-18 17:04 ` Christoph Lameter
2006-08-16 7:51 ` [PATCH2 " Evgeniy Polyakov
2006-08-16 16:57 ` Stephen Hemminger
2006-08-16 19:27 ` Evgeniy Polyakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060814122049.GC18321@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=davem@davemloft.net \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox