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] [day] [month] [year] [list]
Message-ID: <1317828827.6766.37.camel@twins>
Date:	Wed, 05 Oct 2011 17:33:47 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Christoph Lameter <cl@...two.org>
Cc:	starlight@...nacle.cx, Eric Dumazet <eric.dumazet@...il.com>,
	linux-kernel@...r.kernel.org, netdev <netdev@...r.kernel.org>,
	Willy Tarreau <w@....eu>, Ingo Molnar <mingo@...e.hu>
Subject: Re: big picture UDP/IP performance question re 2.6.18  -> 2.6.32

On Wed, 2011-10-05 at 09:26 -0500, Christoph Lameter wrote:
> 
> > Also, for latency, we've got ftrace and a latencytracer, provide traces
> > that illustrate your fail.
> 
> We would need a backport of both to a kernel version that works with
> reasonable latencies so that we can figure out what caused these
> regressions for this particular case. Disabling network and kernel
> features usually gives you better performance but there are a lot of
> things in the hot paths these days that can not be disabled.

Well can can also just take the status quo and use tools like ftrace and
perf to find out what your hot paths are and where you're spending time.

On -rt we use the (irq)latencytracer a _lot_ to find problems, a
detailed function trace of WTH the kernel thinks its doing helps a lot
with trying to fix it.

Things like cyclictest are also useful to find application level
latencies, it can trace the entire latency path if needed.

Kernel level profiles are also a great tool to find out where you're
spending your time.
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ