From: Andi Kleen <ak@suse.de>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: I/OAT: Call for discussion
Date: Thu, 20 Apr 2006 02:49:02 +0200 [thread overview]
Message-ID: <200604200249.03167.ak@suse.de> (raw)
In-Reply-To: <5389061B65D50446B1783B97DFDB392D8E9F0A@orsmsx411.amr.corp.intel.com>
On Wednesday 19 April 2006 18:39, Grover, Andrew wrote:
> We have posted all the performance data we have gathered so far on the
> linux-net wiki: http://linux-net.osdl.org/index.php/I/OAT , and listed
> the overall concerns that have been expressed in private. I'm hoping you
> will look at the data, re-examine the patches, and then we can talk
> about the technical issues here on the list, getting down to the
> specifics, so we can hash it out in public and settle on the right path
> to take.
Maybe it would be best if you just reposted the patches?
-Andi
next prev parent reply other threads:[~2006-04-20 0:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 16:39 I/OAT: Call for discussion Grover, Andrew
2006-04-19 17:12 ` Stephen Hemminger
2006-04-19 17:28 ` John Ronciak
2006-04-19 21:44 ` Christoph Hellwig
2006-04-20 15:17 ` Jack Vogel
2006-04-20 15:26 ` Arnaldo Carvalho de Melo
2006-04-20 0:49 ` Andi Kleen [this message]
2006-04-20 4:12 ` Andrew Grover
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=200604200249.03167.ak@suse.de \
--to=ak@suse.de \
--cc=andrew.grover@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).