All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: chris.leech@gmail.com
Cc: "David S. Miller" <davem@davemloft.net>,
	olof@lixom.net, andrew.grover@intel.com, netdev@vger.kernel.org
Subject: Re: [PATCH 0/10] [IOAT] I/OAT patches repost
Date: Thu, 27 Apr 2006 16:53:25 -0700	[thread overview]
Message-ID: <44515975.3090109@hp.com> (raw)
In-Reply-To: <41b516cb0604271649o31315086ma1c82b824da263e7@mail.gmail.com>

Chris Leech wrote:
>>Netperf2 TOT now accesses the buffer that was just recv()'d rather than
>>the one that is about to be recv()'d.
> 
> 
> We've posted netperf2 results with I/OAT enabled/disabled and the data
> access option on/off at
> http://kernel.org/pub/linux/kernel/people/grover/ioat/netperf-icb-1.5-postscaling-both.pdf
> 

calling it netperf data verification is a quite overstated - all netperf 
does is read from or write to the buffer.  there is no check of data 
integrity or anything

rick jones

  reply	other threads:[~2006-04-27 23:53 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 [this message]
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=44515975.3090109@hp.com \
    --to=rick.jones2@hp.com \
    --cc=andrew.grover@intel.com \
    --cc=chris.leech@gmail.com \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.