From: "Changli Gao" <xiaosuo@gmail.com>
To: "Octavian Purdila" <opurdila@ixiacom.com>
Cc: netdev@vger.kernel.org, "Jens Axboe" <jens.axboe@oracle.com>
Subject: Re: TCP receive splice performance
Date: Mon, 12 May 2008 21:01:16 +0800 [thread overview]
Message-ID: <412e6f7f0805120601h1121deaewd69ecebc744f258d@mail.gmail.com> (raw)
In-Reply-To: <200805121545.50390.opurdila@ixiacom.com>
On Mon, May 12, 2008 at 8:45 PM, Octavian Purdila <opurdila@ixiacom.com> wrote:
>
> In the second test case the same test was performed, only this time with some
> modification in the network stack to disable the copying from/to userspace.
> Throughput was 122-123MB which is practically line-rate.
It is interesting. Could you show us your modification?
--
Regards，
Changli Gao(xiaosuo@gmail.com)
next prev parent reply other threads:[~2008-05-12 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 12:45 TCP receive splice performance Octavian Purdila
2008-05-12 13:01 ` Changli Gao [this message]
2008-05-14 9:01 ` [RFC] [PATCH] TCP read/write ignore (was TCP receive splice performance) Octavian Purdila
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=412e6f7f0805120601h1121deaewd69ecebc744f258d@mail.gmail.com \
--to=xiaosuo@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.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).