Re: [PATCH] Cpuset: rcu optimization of page alloc hook

On Tue, 13 Dec 2005, Paul Jackson wrote:

> So my intuition is:
>   If read alot but seldom written, mark "__read_mostly".
>   If seldom read or written, leave unmarked.

Correct.

>   1) I would -not- mark "struct kmem_cache *cpuset" __read_mostly, as it
>      is rarely accessed on -any- code path, much less a hot one.  It is
>      ideal cannon fodder.

Agree.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH] Cpuset: rcu optimization of page alloc hook
  - From: Paul Jackson <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
  - From: Eric Dumazet <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
  - From: Paul Jackson <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
  - From: Andrew Morton <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
  - From: Paul Jackson <[email protected]>

Prev by Date: Re: [PATCH 3/3] sanitize building of fs/compat_ioctl.c
Next by Date: Re: [PATCH 1/19] MUTEX: Introduce simple mutex implementation
Previous by thread: Re: [PATCH] Cpuset: rcu optimization of page alloc hook
Next by thread: parport module is a missing "dev" file
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]