netdev - RE: [patch 1/4] - Potential performance bottleneck for Linxu TCP

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: <HNEBLGGMEGLPMPPDOPMGAEAOCGAA.wenji@fnal.gov>
Date:	Thu, 30 Nov 2006 14:58:00 -0600
From:	Wenji Wu <wenji@...l.gov>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Evgeniy Polyakov <johnpol@....mipt.ru>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	David Miller <davem@...emloft.net>, akpm@...l.org,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: RE: [patch 1/4] - Potential performance bottleneck for Linxu TCP

>if you still have the test-setup, could you nevertheless try setting the
>priority of the receiving TCP task to nice -20 and see what kind of
>performance you get?

A process with nice of -20 can easily get the interactivity status. When it
expires, it still go back to the active array. It just hide the TCP problem,
instead of solving it.

For a process with nice value of -20, it will have the following advantages
over other processes:
(1) its timeslice is 800ms, the timeslice of a process with a nice value of
0 is 100ms
(2) it has higher priority than other processes
(3) it is easier to gain the interactivity status.

The chances that the process expires and moves to the expired array with
packets within backlog is much reduces, but still has the chance.

wenji

-
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