From: Florian Weimer <fw@deneb.enyo.de>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: write barriers - Was: Re: [RFC][PATCH] problem of cont_prepare_write()
Date: Thu, 13 Jan 2005 19:08:10 +0100 [thread overview]
Message-ID: <87is61gq2d.fsf@deneb.enyo.de> (raw)
In-Reply-To: <41E69A28.9080900@nortelnetworks.com> (Chris Friesen's message of "Thu, 13 Jan 2005 09:56:24 -0600")
* Chris Friesen:
> I believe so. You may also need to cast them as volatile to prevent the
> compiler from reordering--can someone with more gcc knowledge than I
> state definitively whether or not it is smart enough to not reorder
> barriers?
If you define it properly, GCC won't reorder it (volatile __asm__ with
memory operands should be sufficient).
next prev parent reply other threads:[~2005-01-13 18:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 10:30 [RFC][PATCH] problem of cont_prepare_write() OGAWA Hirofumi
2004-11-22 10:41 ` Andrew Morton
2004-11-22 10:46 ` Andrew Morton
2004-11-22 11:03 ` Anton Altaparmakov
2004-11-22 21:53 ` Andrew Morton
2004-11-22 23:30 ` Anton Altaparmakov
2004-11-22 23:43 ` Andrew Morton
2005-01-13 14:47 ` write barriers - Was: " Anton Altaparmakov
2005-01-13 15:56 ` Chris Friesen
2005-01-13 18:08 ` Florian Weimer [this message]
2004-11-22 11:38 ` OGAWA Hirofumi
2004-11-22 21:43 ` Andrew Morton
2004-11-23 2:22 ` OGAWA Hirofumi
2004-11-23 2:30 ` Andrew Morton
2004-11-23 2:55 ` OGAWA Hirofumi
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=87is61gq2d.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=cfriesen@nortelnetworks.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 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.