From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: write_unlock: replace clear_bit with byte store
Date: Fri, 29 Apr 2005 15:51:53 +0000 [thread overview]
Message-ID: <20050429155153.GA8928@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0504281329150.23584@schroedinger.engr.sgi.com>
On Fri, Apr 29, 2005 at 08:48:43AM -0700, David Mosberger wrote:
> >> Yes, but _if_ it's a good idea to use .nta with GCC, there is no
> >> reason not to do the same with ICC. Don't introduce unnecessary
> >> divergence.
>
> Christoph> The same situation of .nta only for GCC already exists
> Christoph> for regular spinlocks as a result of my nta unlock patch
> Christoph> that I posted a week or so ago.
>
> And that's an argument to make the situation worse? How about
> cleaning up the previous patch instead?
I don't think it's fair to expect contributors to fix up ifdef'ed bits for
a propritary compiler. If HP and Intel care about it they can add the
features for icc later.
next prev parent reply other threads:[~2005-04-29 15:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 20:32 write_unlock: replace clear_bit with byte store Christoph Lameter
2005-04-28 20:43 ` David Mosberger
2005-04-28 20:53 ` Christoph Lameter
2005-04-28 22:05 ` Christoph Lameter
2005-04-28 22:25 ` Zou, Nanhai
2005-04-28 22:51 ` Christoph Lameter
2005-04-28 23:55 ` Chen, Kenneth W
2005-04-29 0:21 ` Christoph Lameter
2005-04-29 0:28 ` Chen, Kenneth W
2005-04-29 0:50 ` Christoph Lameter
2005-04-29 1:04 ` Chen, Kenneth W
2005-04-29 1:48 ` Chen, Kenneth W
2005-04-29 7:09 ` David Mosberger
2005-04-29 11:37 ` David Mosberger
2005-04-29 15:19 ` Christoph Lameter
2005-04-29 15:20 ` Christoph Lameter
2005-04-29 15:24 ` David Mosberger
2005-04-29 15:28 ` David Mosberger
2005-04-29 15:30 ` Christoph Lameter
2005-04-29 15:38 ` David Mosberger
2005-04-29 15:46 ` Christoph Lameter
2005-04-29 15:48 ` David Mosberger
2005-04-29 15:51 ` Christoph Hellwig [this message]
2005-04-29 15:55 ` Christoph Lameter
2005-04-29 16:01 ` David Mosberger
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=20050429155153.GA8928@infradead.org \
--to=hch@infradead.org \
--cc=linux-ia64@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