From: Arjan van de Ven <arjan@infradead.org>
To: tim.c.chen@linux.intel.com
Cc: linux-kernel@vger.kernel.org, davem@sunset.davemloft.net,
kuznet@ms2.inr.ac.ru, netdev@vger.kernel.org
Subject: Re: 2.6.19-rc1: Volanomark slowdown
Date: Wed, 08 Nov 2006 16:55:18 +0100 [thread overview]
Message-ID: <1163001318.3138.346.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1162924354.10806.172.camel@localhost.localdomain>
On Tue, 2006-11-07 at 10:32 -0800, Tim Chen wrote:
> The patch
>
> [TCP]: Send ACKs each 2nd received segment
> commit: 1ef9696c909060ccdae3ade245ca88692b49285b
> http://kernel.org/git/?
> p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1ef9696c909060ccdae3ade245ca88692b49285b
>
> reduced Volanomark benchmark throughput by 10%.
> This is because Volanomark sends
> short message (<100 bytes) on its TCP
> connections. This patch increases the number of ACKs
> traffic by 3.5 times.
>
> By adopting this patch, we assume that with
> small segment, having short delay is important
> enough that we are willing to reduce bandwidth
> with more ACKs.
I wonder if it's an option to use low priority QoS fields for these acks
(heck I don't even know if ACKs have such fields in their packet) so
that they can get dropped if there are more packets then there is
bandwidth ....
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2006-11-08 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 18:32 Tim Chen
2006-11-08 15:55 ` Arjan van de Ven [this message]
2006-11-08 16:29 ` Olaf Kirch
2006-11-08 18:38 ` Tim Chen
2006-11-08 19:44 ` Arjan van de Ven
2006-11-08 22:10 ` Olaf Kirch
2006-11-08 22:07 ` Tim Chen
2006-11-08 23:00 ` Stephen Hemminger
2006-11-08 22:32 ` Tim Chen
2006-11-09 9:21 ` Olaf Kirch
2006-11-08 22:58 ` Stephen Hemminger
2006-11-09 1:08 ` Rick Jones
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=1163001318.3138.346.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=davem@sunset.davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tim.c.chen@linux.intel.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
all inboxes | Powered by JetHome®