From: "Shigeo N" <shigeonx@gmail.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: "Andi Kleen" <andi@firstfloor.org>,
LKML <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Subject: Re: XTP for 2.6.25
Date: Wed, 7 May 2008 13:32:01 +0900 [thread overview]
Message-ID: <18b669d80805062132m618e0e1fwf92bbb2ced393cb@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0804251115470.2363@wrl-59.cs.helsinki.fi>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 2407 bytes --]
I tested again on Linux 2.6.25 with TCP reordering patch.Of course, TCP performance was improved.
Here is the result.
case2-2) random delay (with TCP reordering patch)
In this case, add a fixed amount of delay + 10% random delay by command, "tc change dev eth0 root netem delay 100ms 10ms 25%".
fixed delay UDP/TCP/XTP throghput --------------------------------------- 10ms 88/85/92 Mbps 30ms 88/67/91 Mbps 50ms 88/58/89 Mbps 70ms 88/43/80 Mbps 100ms 88/26/66 Mbps
case2) random delay (without TCP reordering patch)
In this case, add a fixed amount of delay + 10% random delay by command, "tc change dev eth0 root netem delay 100ms 10ms 25%".
fixed delay UDP/TCP/XTP throghput --------------------------------------- 10ms 88/80/92 Mbps 30ms 88/51/91 Mbps 50ms 88/41/89 Mbps 70ms 88/28/80 Mbps 100ms 88/19/66 Mbps
case1) fixed delay
In this case, just adds a fixed amount of delay to all packets going out by command, "tc qdisc add dev eth0 root netem delay 100ms".
fixed delay UDP/TCP/XTP throghput --------------------------------------- 10ms 88/85/92 Mbps 30ms 88/70/91 Mbps 50ms 88/63/89 Mbps 70ms 88/52/84 Mbps 100ms 88/36/70 Mbps
Thanks,
On Fri, Apr 25, 2008 at 5:23 PM, Ilpo Järvinen<ilpo.jarvinen@helsinki.fi> wrote:> On Fri, 25 Apr 2008, Shigeo N wrote:>>> case2) random delay>>>> In this case, add a fixed amount of delay + 10% random delay by>> command, "tc change dev eth0 root netem delay 100ms 10ms 25%".>>>> Here is the result.>>>> fixed delay UDP/TCP/XTP throghput>> --------------------------------------->> 10ms 88/80/92 Mbps>> 30ms 88/51/91 Mbps>> 50ms 88/41/89 Mbps>> 70ms 88/28/80 Mbps>> 100ms 88/19/66 Mbps>>>> TCP's perfomance looks very poor when delay is long and variable.>> Where these results with 2.6.25 as well? ...John Heffner just couple of> days ago fixed reordering related problem in TCP (in case that netem> parametrization causes reordering), the fix is not even in 2.6.24.y, I> think...>> --> i.>ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
prev parent reply other threads:[~2008-05-07 4:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 10:14 Shigeo N
2008-04-24 10:30 ` David Miller
2008-04-24 11:27 ` Andi Kleen
2008-04-24 13:06 ` Shigeo N
2008-04-25 7:59 ` Shigeo N
2008-04-25 8:23 ` Ilpo Järvinen
2008-04-25 8:28 ` David Miller
2008-04-25 8:51 ` Shigeo N
2008-04-25 8:55 ` David Miller
2008-04-25 13:05 ` Ilpo Järvinen
2008-04-25 20:12 ` David Miller
2008-04-25 21:06 ` Ilpo Järvinen
2008-05-07 4:32 ` Shigeo N [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=18b669d80805062132m618e0e1fwf92bbb2ced393cb@mail.gmail.com \
--to=shigeonx@gmail.com \
--cc=andi@firstfloor.org \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®