linux-kernel - TLB evaluation for Linux

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

Message-ID: <1942732773.182121220328723728.JavaMail.osg@osgjas04.cns.ufl.edu>
Date:	Tue, 2 Sep 2008 00:12:03 -0400 (EDT)
From:	"CHADHA,VINEET" <vineet@....edu>
To:	nickpiggin@...oo.com.au
Cc:	linux-kernel@...r.kernel.org, vineet@....edu
Subject: TLB evaluation for Linux

Hi,

I have been working to evaluate TLB performance for Linux O/S and 
virtualized workloads(such as Xen) in a Full system simulator(e.g. 
simics). While my evaluation is in nascent stage, I do notice that 
most of the IPIs in multi-core environments cause complete TLB 
Flush.

I want to evaluate cost of TLB shootdown including re-population 
vs. each entry shootdown (invlpg). While a similar study has been 
done in other kernels (e.g. L4 kernel), I am not aware if it has 
been done for Linux O/S.

Are there hooks or patches to test or evaluate TLB performance. 
Specifically, I would like to know where to make changes in Linux 
kernel to support each entry shootdown.

Questions may sound little naive, but any pointers or related work 
will be helpful to me.

Thanks in advance.

Regards,
Vineet

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