* naïve question
@ 2006-04-20 17:30 Massimiliano Hofer
0 siblings, 0 replies; only message in thread
From: Massimiliano Hofer @ 2006-04-20 17:30 UTC (permalink / raw)
To: netfilter-devel
Hi,
I noticed in various part of the kernel that there are assignments on live
kernel structures without locks to protect them (of course there are proper
memory barriers).
Example from ipt_recent.c:
curr_table->status_proc->read_proc = ip_recent_get_info;
curr_table->status_proc->write_proc = ip_recent_ctrl;
I know that on a x86 a 32 bit assignment is atomic (I'm not sure about 386SXs)
and the same goes for x86_64 and 64 bit pointer, but I'm not sure that it
really works on other architectures.
I didn't find documentation about it. Is it just a normal practice due to the
fact that exotic archs with odd bus widths aren't usually SMP or is it
guaranteed?
--
Saluti,
Massimiliano Hofer
Nucleus
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-04-20 17:30 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-04-20 17:30 naïve question Massimiliano Hofer
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.