Re: SELinux performance issue with large systems (32 cpus)

From: Valdis . Kletnieks
Date: Tue Nov 23 2004 - 16:05:06 EST


On Tue, 23 Nov 2004 11:22:05 PST, keith said:

> After some lock profiling (keeping track of what locks were last used
> and how many cycles were spent waiting) it became quite clean the the
> avc_lock was to blame. The avc_lock is a SELinux lock.

Known issue - in the -mm kernels there are these patches:

selinux-scalability-add-spin_trylock_irq-and.patch
SELinux scalability: add spin_trylock_irq and spin_trylock_irqsave

selinux-scalability-convert-avc-to-rcu.patch
SELinux scalability: convert AVC to RCU

selinux-atomic_dec_and_test-bug.patch
SELinux: atomic_dec_and_test() bug

selinux-scalability-avc-statistics-and-tuning.patch
SELinux scalability: AVC statistics and tuning

I don't know if these patches require other infrastructure from the -mm
patchseries, or if they'll apply clean to a 2.6.10-rc2 kernel.


Attachment: pgp00000.pgp
Description: PGP signature