From: Massimiliano Hofer <max@nucleus.it>
To: netfilter-devel@lists.netfilter.org
Subject: naïve question
Date: Thu, 20 Apr 2006 19:30:49 +0200 [thread overview]
Message-ID: <200604201930.49748.max@nucleus.it> (raw)
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
reply other threads:[~2006-04-20 17:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200604201930.49748.max@nucleus.it \
--to=max@nucleus.it \
--cc=netfilter-devel@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.