From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Jesper Juhl <jesper.juhl@gmail.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Heikki Orsila <shdl@zakalwe.fi>, "H. Peter Anvin" <hpa@zytor.com>,
Satyam Sharma <satyam.sharma@gmail.com>
Subject: Re: [PATCH] "volatile considered harmful", take 2
Date: Fri, 11 May 2007 13:17:32 +0200 [thread overview]
Message-ID: <464450CC.7010002@s5r6.in-berlin.de> (raw)
In-Reply-To: <6143.1178828419@lwn.net>
Jonathan Corbet wrote:
> +The key point to understand with regard to volatile is that its purpose is
> +to suppress optimization, which is almost never what one really wants to
> +do. In the kernel, one must protect shared data structures against
> +unwanted concurrent access, which is very much a different task. As it
> +happens, once the critical sections are properly implemented, the compiler
> +optimization issues which volatile was added to prevent will have been
> +taken care of in a more efficient way.
The "As it happens... efficient way." sentence is hard to read: It is
long and nested like in German, combined with several English
ambiguities (e.g. WRT noun vs. verb vs. adjective). Maybe just leave
this sentence out, as it is redundant to later statements like "In
properly-written kernel code, volatile can only serve to slow things down".
--
Stefan Richter
-=====-=-=== -=-= -=-==
http://arcgraph.de/sr/
prev parent reply other threads:[~2007-05-11 11:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 20:20 Jonathan Corbet
2007-05-10 20:38 ` jimmy bahuleyan
2007-05-10 21:44 ` Satyam Sharma
2007-05-11 12:21 ` Johannes Stezenbach
2007-05-11 13:52 ` jimmy bahuleyan
2007-05-11 14:21 ` Satyam Sharma
2007-05-10 21:34 ` Jan Engelhardt
2007-05-10 21:45 ` H. Peter Anvin
2007-05-11 21:33 ` Jan Engelhardt
2007-05-11 21:47 ` H. Peter Anvin
[not found] ` <64026d4a0705112157p75d76956g40455c7402b096d6@mail.gmail.com>
2007-05-12 5:32 ` H. Peter Anvin
2007-05-11 7:41 ` Philipp Matthias Hahn
2007-05-11 8:41 ` Bernd Eckenfels
2007-05-11 11:17 ` Stefan Richter [this message]
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=464450CC.7010002@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=satyam.sharma@gmail.com \
--cc=shdl@zakalwe.fi \
/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
Powered by JetHome