[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48D1194D.3060003@cosmosbay.com>
Date: Wed, 17 Sep 2008 16:50:53 +0200
From: Eric Dumazet <dada1@...mosbay.com>
To: Mike Galbraith <efault@....de>
Cc: Ingo Molnar <mingo@...e.hu>,
Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>,
Christoph Lameter <cl@...ux-foundation.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
LKML <linux-kernel@...r.kernel.org>,
kernel-testers@...r.kernel.org
Subject: Re: [Bug #11308] tbench regression on each kernel release from 2.6.22
-> 2.6.28
Eric Dumazet a écrit :
> Mike Galbraith a écrit :
>> I sure hope it's something like ping-pong, it's driving me NUTS.
>
> Could you please try following patch ?
>
> [PATCH] security_ops moved to read_mostly section
>
> "struct security_operations *security_ops" should be moved to
> read_mostly section in order to NOT let it share a cache line with higly
> modified variables.
>
> Signed-off-by: Eric Dumazet <dada1@...mosbay.com>
>
> diff --git a/security/security.c b/security/security.c
> index 3a4b4f5..0b13d65 100644
> --- a/security/security.c
> +++ b/security/security.c
> @@ -24,7 +24,7 @@ static __initdata char chosen_lsm[SECURITY_NAME_MAX + 1];
> extern struct security_operations default_security_ops;
> extern void security_fixup_ops(struct security_operations *ops);
>
> -struct security_operations *security_ops; /* Initialized to NULL */
> +struct security_operations *security_ops __read_mostly;e
Sorry for the extra 'e' at the end of this line, please remove it :)
>
> /* amount of vm to protect from userspace access */
> unsigned long mmap_min_addr = CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR;
>
--
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/
Powered by blists - more mailing lists