From: "David S. Miller" <davem@davemloft.net>
To: olof@lixom.net
Cc: andy.grover@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH 0/10] [IOAT] I/OAT patches repost
Date: Thu, 20 Apr 2006 17:44:38 -0700 (PDT) [thread overview]
Message-ID: <20060420.174438.15249396.davem@davemloft.net> (raw)
In-Reply-To: <20060420233343.GL26746@pb15.lixom.net>
From: Olof Johansson <olof@lixom.net>
Date: Thu, 20 Apr 2006 18:33:43 -0500
> On Thu, Apr 20, 2006 at 03:14:15PM -0700, Andrew Grover wrote:
> > In
> > addition, there may be workloads (file serving? backup?) where we
> > could do a skb->page-in-page-cache copy and avoid cache pollution?
>
> Yes, NFS is probably a prime example of where most of the data isn't
> looked at; just written to disk. I'm not sure how well-optimized the
> receive path is there already w.r.t. avoiding copying though. I don't
> remember seeing memcpy and friends being high on the profile when I
> looked at SPECsfs last.
If that makes sense then the cpu copy can be made to use non-temporal
stores.
next prev parent reply other threads:[~2006-04-21 0:44 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 [this message]
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
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=20060420.174438.15249396.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy.grover@gmail.com \
--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).