From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dborkman@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
	by huchra.bufferbloat.net (Postfix) with ESMTP id 6AD1121F181
	for <bloat-devel@lists.bufferbloat.net>;
	Tue, 18 Mar 2014 08:49:13 -0700 (PDT)
Received: from int-mx02.intmail.prod.int.phx2.redhat.com
	(int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s2IFn9ce031106
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Tue, 18 Mar 2014 11:49:10 -0400
Received: from [10.36.4.247] (vpn1-4-247.ams2.redhat.com [10.36.4.247])
	by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP
	id s2IFn7dS010086
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 18 Mar 2014 11:49:08 -0400
Message-ID: <53286AF2.3010203@redhat.com>
Date: Tue, 18 Mar 2014 16:49:06 +0100
From: Daniel Borkmann <dborkman@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Jesper Dangaard Brouer <brouer@redhat.com>
Subject: Re: Linux SCTP: what kind of performance should I expect from netperf?
References: <CAA93jw4-c7ARyqCO_46DJi64-4gjZH8CT-bDNo8OrMXnM3Crtg@mail.gmail.com>
	<20140318161658.619158b9@redhat.com>
In-Reply-To: <20140318161658.619158b9@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on 10.5.11.12
Cc: netperf-dev@netperf.org, bloat-devel <bloat-devel@lists.bufferbloat.net>
X-BeenThere: bloat-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Developers working on AQM, device drivers,
	and networking stacks" <bloat-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat-devel>,
	<mailto:bloat-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat-devel>
List-Post: <mailto:bloat-devel@lists.bufferbloat.net>
List-Help: <mailto:bloat-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat-devel>,
	<mailto:bloat-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Tue, 18 Mar 2014 15:49:13 -0000

On 03/18/2014 04:16 PM, Jesper Dangaard Brouer wrote:
>
> Hi Daniel,
>
> Can you give some input on this thread?
>
> On Tue, 18 Mar 2014 10:53:40 -0400 Dave Taht <dave.taht@gmail.com> wrote:
>
>> I was curious about sctp's performance characteristics on
>> AQM'd systems... so
>> I built netperf with sctp support, and ran a couple tests on
>> kernel 3.11...
>>
>> +1: SCTP appears to work over IPv6
>> -1: Throughput is terrible

Yes, performance sucks so far (it's a known problem) and
we need to work on it ... ;-)

I presume one reason here could be as well that you need to
do crc32c checksumming on software (what does perf say?).

>> d@nuc:~/git/netperf$ netperf -6 -H snapon.lab.bufferbloat.net -t
>> SCTP_STREAM_MANY
>> SCTP 1-TO-MANY STREAM TEST from ::0 (::) port 0 AF_INET6 to
>> snapon.lab.bufferbloat.net () port 0 AF_INET6 : demo
>> Recv   Send    Send
>> Socket Socket  Message  Elapsed
>> Size   Size    Size     Time     Throughput
>> bytes  bytes   bytes    secs.    10^6bits/sec
>>
>> 212992 212992   4096    10.00       0.31
>> d@nuc:~/git/netperf$ netperf -6 -H snapon.lab.bufferbloat.net -t TCP_MAERTS
>> MIGRATED TCP MAERTS TEST from ::0 (::) port 0 AF_INET6 to
>> snapon.lab.bufferbloat.net () port 0 AF_INET6 : demo
>> Recv   Send    Send
>> Socket Socket  Message  Elapsed
>> Size   Size    Size     Time     Throughput
>> bytes  bytes   bytes    secs.    10^6bits/sec
>>
>>   87380  16384  16384    10.00       7.65