From: Jamie Lokier <jamie@shareable.org>
To: "odain2@mindspring.com" <odain2@mindspring.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_PACKET_MMAP revisited
Date: Wed, 29 Oct 2003 04:50:32 +0000 [thread overview]
Message-ID: <20031029045032.GA27546@mail.shareable.org> (raw)
In-Reply-To: <176730-2200310329491330@M2W026.mail2web.com>
odain2@mindspring.com wrote:
> Alan Cox pointed out that the main cost of the memory copy is
> getting the data from system memory (where the NIC put it via DMA)
> into the L1 cache (DMA doesn't do any cache coherence so it can't go
> there directly). The memory copy (presumably from L1 cache to L1
> cache) is insignificant compared to this cost and since you'll need
> to get the data into L1 cache to use it anyway, the memory copy is
> virtually free.
After the data is copied, it's likely to be written from L1 to L2 (at
least) before that position in the ring buffer is rewritten, so that's
another overhead.
-- Jamie
next prev parent reply other threads:[~2003-10-29 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 4:09 CONFIG_PACKET_MMAP revisited odain2
2003-10-29 4:50 ` Jamie Lokier [this message]
2003-11-06 11:08 ` Gianni Tedesco
2003-11-06 14:13 ` Oliver Dain
2003-11-06 14:31 ` Gianni Tedesco
2003-11-06 15:29 ` P
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=20031029045032.GA27546@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=odain2@mindspring.com \
/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;
as well as URLs for NNTP newsgroup(s).