linux-kernel - Re: Performance degradation measurement [was Re: [PATCH 06/37] Security: Separate task security context from task

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: <17671.1206276048@redhat.com>
Date:	Sun, 23 Mar 2008 12:40:48 +0000
From:	David Howells <dhowells@...hat.com>
To:	Valdis.Kletnieks@...edu
Cc:	dhowells@...hat.com, akpm@...ux-foundation.org, torvalds@...l.org,
	Trond.Myklebust@...app.com, chuck.lever@...cle.com,
	nfsv4@...ux-nfs.org, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, selinux@...ho.nsa.gov,
	linux-security-module@...r.kernel.org
Subject: Re: Performance degradation measurement [was Re: [PATCH 06/37] Security: Separate task security context from task_struct [ver #34]]

Valdis.Kletnieks@...edu wrote:

> What's up with *that*?  The *fastest* run with it disabled is 1.118, and
> the *slowest* with it enabled is 1.119.  At that point, I have to wonder
> what we're really measuring here....

That's a good point.  I missed that, probably because I *knew* it would be
slower with SELinux enabled, and so just assumed that it was.

That's really odd. There should be no disk accesses happening (the
pagecache/buffer cache is preloaded and noatime is turned on), the CPUs are
running at top speed at all times, and there's lots of free RAM available.
Network activity should also be minimal, so I'm not sure why there's so much
variance.

I'll re-run my tests from a kernel running a single bash and nothing else, see
if I can get more consistent data.

David
--
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/