netdev - Re: [PATCH] net_sched: sfq: add optional RED on top of SFQ

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAA93jw5bb48sNt_nhKx2O-Sxjzzi7gvfXE6YRgxkYZxEMru0HA@mail.gmail.com>
Date:	Fri, 6 Jan 2012 21:26:48 +0100
From:	Dave Taht <dave.taht@...il.com>
To:	Rick Jones <rick.jones2@...com>
Cc:	Eric Dumazet <eric.dumazet@...il.com>,
	David Miller <davem@...emloft.net>,
	netdev <netdev@...r.kernel.org>,
	Stephen Hemminger <shemminger@...tta.com>,
	Kathleen Nichols <nichols@...lere.com>,
	Jim Gettys <jg@...edesktop.org>
Subject: Re: [PATCH] net_sched: sfq: add optional RED on top of SFQ

On Fri, Jan 6, 2012 at 8:43 PM, Rick Jones <rick.jones2@...com> wrote:
> On 01/06/2012 11:33 AM, Eric Dumazet wrote:
>>
>> Le vendredi 06 janvier 2012 à 10:30 -0800, Rick Jones a écrit :
>>
>>> netperf nitpick :)  While I doubt that Dave Taht is running it that way,
>>> one can have multiple requests in flight on a single _RR test via the
>>> test-specific -b<additionaltrans>  option.  That option is enabled by
>>> default (--enable-burst on the configure) in 2.5.0 and later.
>>
>>
>> Ah Rick, I dont think we can tune IP_TOS with netperf -t UDP_{STREAM|
>> RR} ?
>>
>> I ask because it could be a good thing to set ECT(0) on datagrams to
>> check our ECN capabilities and get in the final report from receiver a
>> count/percentage of CE frames.

For other apps than netperf, being able to see this stuff in iptables
(ip6tables) might be helpful. Did this kernel patch series make it?

http://comments.gmane.org/gmane.comp.security.firewalls.netfilter.devel/41139


>
> Funny you should mention that :)  In the top-of-trunk (perhaps it is in
> 2.5.0 too, I do not recall) there is the global -Y option:
>
> $ src/netperf -Y
> src/netperf: option requires an argument -- 'Y'
>
> Usage: netperf [global options] -- [test options]
>
> Global options:
> ...
>    -y local,remote   Set the socket priority
>    -Y local,remote   Set the IP_TOS. Use hexadecimal.
>
> So long as you either use the omni code directly, or indirectly by not
> undoing WANT_MIGRATION those should work - for some definition of work
> anyway...I would not be surprised to learn there are bugs in the support.

Also in top of netperf trunk is a mode to be able to exercise different TCP
congestion control algorithms. I was mostly fiddling with westwood, tcp-lp and
tcp-ledbat v1 ( https://github.com/silviov/TCP-LEDBAT )

" The output selectors are LOCAL_CONG_CONTROL and
   REMOTE_CONG_CONTROL and setting is via the test-specific -K option."

I also have a rsync patch for priority, diffserv and congestion control
floating about...

I'm a little vague as to whether your related kernel patch for inheriting
the congestion algorithm made it in?

I note that netperf trunk breaks backward compatibility with
netperf 2.5.

> However, there is nothing presently in the netperf code to cause any
> *individual* send to be so marked independently of the others.

Heh.

>
> happy benchmarking,
>
> rick jones



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html