On Mon, 26 Jun 2006, Paul Jackson wrote:
> In other words, the name __read_mostly is a little misleading, in my
> book. That name only suggests read much more than written. In your
> words:
>
> something like 99:1 read
99:1 may be too small a ratio.
A read_mostly marked variable should be changed rarely (meaning is
is extremely unlikely that his is going to change) but read frequently.
F.e. configuration data for timer operations, number of possible
processors and stuff like that.
If we would make the operation to write to the read_mostly section more
expensive (by f.e. replicating the data per node) then this would hold off
the uses that are changing too frequently.
-
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/
[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]
