linux-kernel - Measuring page faults

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>] [day] [month] [year] [list]

Message-ID: <2aa71ac70911200606tdf97f3lbc718046ca14d332@mail.gmail.com>
Date:	Fri, 20 Nov 2009 09:06:33 -0500
From:	Mike Gagnon <mikegagnon@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Measuring page faults

Hi all,

I would like to measure the latency (execution time) of Linux page
faults.  I tried using lmbench, but I get unrealistically fast results
from the lmbench lat_pagefault benchmark.  The problem seems to be
that lmbench attempts to ensure pages are paged out using msync with
the MS_INVALIDATE flag set, but this doesn't seem to cause page outs
on Linux.  http://www.bitmover.com/lmbench/lat_pagefault.8.html

I would like to adapt lmbench to correctly measure page faults on
Linux, but I need a mechanism to ensure specific pages are paged-out.
Is there a good way to reliably cause page-outs in Linux (so that I
may then cause page faults by touching the paged-out pages)?

Thanks,
Michael Gagnon
--
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/