From: Ingo Oeser <netdev@axxeo.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: olof@lixom.net, andrew.grover@intel.com, netdev@vger.kernel.org,
Ingo Oeser <ioe-lkml@rameria.de>
Subject: Re: [PATCH 0/10] [IOAT] I/OAT patches repost
Date: Fri, 21 Apr 2006 19:13:57 +0200 [thread overview]
Message-ID: <200604211913.57350.netdev@axxeo.de> (raw)
In-Reply-To: <20060420.172742.132879746.davem@davemloft.net>
David S. Miller wrote:
> The first thing an application is going to do is touch that data. So
> I think it's very important to prewarm the caches and the only
> straightforward way I know of to always warm up the correct cpu's
> caches is copy_to_user().
Hmm, what if the application is sth. like a MPEG demultiplexer?
There you don't like to look at everything and excplicitly
ignore received data[1].
Yes, I know this is usually done with hardware demuxers and filters,
but the principle might apply to other applications as well, for which
no hardware solutions exist.
Regards
Ingo Oeser
[1] which you cannot ignore properly with Linux yet.
prev parent reply other threads:[~2006-04-21 17:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 20:49 [PATCH 0/10] [IOAT] I/OAT patches repost Andrew Grover
2006-04-20 21:33 ` Olof Johansson
2006-04-20 22:14 ` Andrew Grover
2006-04-20 23:33 ` Olof Johansson
2006-04-21 0:44 ` David S. Miller
2006-04-21 3:09 ` Olof Johansson
2006-04-21 0:38 ` David S. Miller
2006-04-21 1:02 ` Rick Jones
2006-04-21 2:23 ` Herbert Xu
2006-04-21 0:27 ` David S. Miller
2006-04-21 1:00 ` Rick Jones
2006-04-21 1:13 ` David S. Miller
2006-04-21 17:12 ` Rick Jones
2006-04-27 23:49 ` Chris Leech
2006-04-27 23:53 ` Rick Jones
2006-04-21 3:04 ` Olof Johansson
2006-04-21 3:42 ` David S. Miller
2006-04-21 4:42 ` Olof Johansson
2006-04-27 23:45 ` Chris Leech
2006-04-21 17:13 ` Ingo Oeser [this message]
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=200604211913.57350.netdev@axxeo.de \
--to=netdev@axxeo.de \
--cc=andrew.grover@intel.com \
--cc=davem@davemloft.net \
--cc=ioe-lkml@rameria.de \
--cc=netdev@vger.kernel.org \
--cc=olof@lixom.net \
/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).