public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: David Howells <dhowells@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	"Adam J. Richter" <adam@yggdrasil.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Patch: linux-2.5.29 __downgrade_write() for CONFIG_RWSEM_GENERIC_SPINLOCK
Date: Mon, 29 Jul 2002 13:08:22 +0100	[thread overview]
Message-ID: <28935.1027944502@warthog.cambridge.redhat.com> (raw)
In-Reply-To: Message from Roman Zippel <zippel@linux-m68k.org>  of "Mon, 29 Jul 2002 13:42:38 +0200." <Pine.LNX.4.44.0207291336120.28515-100000@serv>


Roman Zippel <zippel@linux-m68k.org>
> > It doesn't appear to make any difference which way it is done. The i386
> > code from both looks the same.
> 
> Then I vote for the simpler version. :)

Maybe... I've got a patch for that variation too.

> BTW even if gcc had problems optimizing that, I'd rather make it explicit,
> that the two variables contain the same information:
> 
> 	activity = sem->activity = 0;
> 	if (!list_empty(&sem->wait_list))
> 		sem = __rwsem_do_wake(sem, activity);
> 
> IMO that's more readable and will still work if gcc had to flush the
> cached information before using it.

Brrr... I don't like that. If I'm going to pass in a second argument, then I
want it to be what Christoph's version because it's more readable and more
obvious what it's doing (and, since the value is constant, the optimiser can
obviously get rid of it easily). I don't think gcc is going to be a problem in
that respect since the activity member is not volatile.

David

  reply	other threads:[~2002-07-29 12:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-28 17:50 Patch: linux-2.5.29 __downgrade_write() for CONFIG_RWSEM_GENERIC_SPINLOCK Adam J. Richter
2002-07-28 18:07 ` Roman Zippel
2002-07-28 18:08 ` Christoph Hellwig
2002-07-28 22:55   ` Roman Zippel
2002-07-29  7:42     ` David Howells
2002-07-29  8:01       ` Roman Zippel
2002-07-29  8:31         ` David Howells
2002-07-29  9:13           ` David Howells
2002-07-29 11:42             ` Roman Zippel
2002-07-29 12:08               ` David Howells [this message]
2002-07-29 12:46                 ` Roman Zippel

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=28935.1027944502@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=adam@yggdrasil.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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