From: Thomas Graf <tgraf@infradead.org>
To: Vladislav Yasevich <vladislav.yasevich@hp.com>
Cc: linux-sctp@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH] sctp: Do not account for sizeof(struct sk_buff) in estimated rwnd
Date: Mon, 19 Dec 2011 18:19:36 -0500 [thread overview]
Message-ID: <20111219231936.GA21801@canuck.infradead.org> (raw)
In-Reply-To: <1324303900-8360-1-git-send-email-tgraf@redhat.com>
On Mon, Dec 19, 2011 at 03:11:40PM +0100, Thomas Graf wrote:
> Trying to reproduce this I found that with the sk_buff overhead removed,
> the performance would improve significantly unless socket buffer limits
> are increased.
I believe this is likely to be misunderstood. What I meant is that by
removing the sk_buff overhead and while using default socket buffer limits
the performance increases as shown below. If socket buffers are enlarged
performance differences fade until there is no longer any difference.
Sorry for poor wording.
> The following numbers have been gathered using a patched iperf
> supporting SCTP over a live 1 Gbit ethernet network. The -l option
> was used to limit DATA chunk sizes. The numbers listed are based on
> the average of 3 test runs each. Default values have been used for
> sk_(r|w)mem.
>
> Chunk
> Size Unpatched No Overhead
> -------------------------------------
> 4 15.2 Kbit [!] 12.2 Mbit [!]
> 8 35.8 Kbit [!] 26.0 Mbit [!]
> 16 95.5 Kbit [!] 54.4 Mbit [!]
> 32 106.7 Mbit 102.3 Mbit
> 64 189.2 Mbit 188.3 Mbit
> 128 331.2 Mbit 334.8 Mbit
> 256 537.7 Mbit 536.0 Mbit
> 512 766.9 Mbit 766.6 Mbit
> 1024 810.1 Mbit 808.6 Mbit
next prev parent reply other threads:[~2011-12-19 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 14:11 [PATCH] sctp: Do not account for sizeof(struct sk_buff) in estimated rwnd Thomas Graf
2011-12-19 20:10 ` David Miller
2011-12-19 23:19 ` Thomas Graf [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-20 5:00 Wei Yongjun
2011-12-20 9:39 ` Thomas Graf
2011-12-20 18:01 ` Vlad Yasevich
2011-12-20 18:59 ` David Miller
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=20111219231936.GA21801@canuck.infradead.org \
--to=tgraf@infradead.org \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vladislav.yasevich@hp.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).