linux-kernel - Re: lmbench ctxsw regression with CFS

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: <20070813.202528.05603304.davem@davemloft.net>
Date:	Mon, 13 Aug 2007 20:25:28 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	akpm@...ux-foundation.org
Cc:	jens.axboe@...cle.com, npiggin@...e.de, mingo@...e.hu,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: lmbench ctxsw regression with CFS

From: Andrew Morton <akpm@...ux-foundation.org>
Date: Mon, 13 Aug 2007 20:00:38 -0700

> Guys, repeat after me: "context switch is not a fast path".  Take
> that benchmark and set fire to it.

Nothing in this world is so absolute :-)

Regardless of the value of lat_ctx, we should thank it for showing
that something is more expensive now.  And it definitely warrants
figuring out what paths are big cycle eaters now and why.

Not "on IA64 indirect calls are expensive, so that must be it", but
rather doing cycle analysis of the relevant scheduling functions to
figure out what might be wrong.

I'm willing to bet it's something completely trivial and easy
to amend, rather than a fundamental issue.  But somebody has
to _look_ instead of supposing this and that.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/