From: Rusty Russell <rusty@rustcorp.com.au>
To: alan@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] kernel locking guide fix.
Date: Wed, 02 May 2001 21:15:53 +1000 [thread overview]
Message-ID: <m14uubp-001QJTC@mozart> (raw)
diff -urN -I \$.*\$ -X /tmp/kerndiff.hKrYxB --minimal linux-2.4.4-official/Documentation/DocBook/kernel-locking.tmpl working-2.4.4-rcu/Documentation/DocBook/kernel-locking.tmpl
--- linux-2.4.4-official/Documentation/DocBook/kernel-locking.tmpl Tue May 1 12:26:15 2001
+++ working-2.4.4-rcu/Documentation/DocBook/kernel-locking.tmpl Wed May 2 21:14:19 2001
@@ -760,8 +760,11 @@
</para>
<para>
- Any atomic operation is defined to act as a memory barrier
- (ie. as per the <function>mb()</function> macro). Also,
+ Some atomic operations are defined to act as a memory barrier
+ (ie. as per the <function>mb()</function> macro, but if in
+ doubt, be explicit.
+ <!-- Rusty Russell 2 May 2001, 2.4.4 -->
+ Also,
spinlock operations act as partial barriers: operations after
gaining a spinlock will never be moved to precede the
<function>spin_lock()</function> call, and operations before
--
Premature optmztion is rt of all evl. --DK
reply other threads:[~2001-05-02 11:12 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=m14uubp-001QJTC@mozart \
--to=rusty@rustcorp.com.au \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox