All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, hzhong@gmail.com
Subject: Re: [PATCH] Profile likely/unlikely macros
Date: Mon, 24 Apr 2006 20:17:25 -0700	[thread overview]
Message-ID: <1145935045.3674.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20060424200657.0af43d6a.akpm@osdl.org>

On Mon, 2006-04-24 at 20:06 -0700, Andrew Morton wrote:
> Daniel Walker <dwalker@mvista.com> wrote:
> >
> >  +	if (likeliness->type & LIKELY_UNSEEN) {
> >  +		if (atomic_dec_and_test(&likely_lock)) {
> >  +			if (likeliness->type & LIKELY_UNSEEN) {
> >  +				likeliness->type &= (~LIKELY_UNSEEN);
> >  +				likeliness->next = likeliness_head;
> >  +				likeliness_head = likeliness;
> >  +			}
> >  +		}
> >  +		atomic_inc(&likely_lock);
> 
> hm, good enough I guess.  It does need a comment explaining why we
> don't just do spin_lock().
> 
> It'd be a bit saner to do
> 
> 	if (!test_and_set_bit(&foo, 0)) {
> 		...
> 		clear_bit(&foo, 0);
> 	}

Ok .. Also a mistaken "define" in the compiler.h .. I'll fix that as
well ..


Daniel



  reply	other threads:[~2006-04-25  3:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25  2:57 [PATCH] Profile likely/unlikely macros Daniel Walker
2006-04-25  3:06 ` Andrew Morton
2006-04-25  3:17   ` Daniel Walker [this message]
2006-04-25 10:11   ` Nick Piggin
2006-04-25 18:06     ` Hua Zhong
2006-04-25 18:23     ` Daniel Walker
2006-04-26  1:08       ` Nick Piggin
2006-04-26  9:56         ` Jörn Engel
2006-04-26 10:07           ` Nick Piggin
2006-04-25 23:14     ` Chen, Kenneth W
2006-04-25  9:19 ` Andreas Mohr
2006-05-01 22:05 ` Roland Dreier
  -- strict thread matches above, loose matches on Subject: below --
2006-04-25  9:15 Mikael Pettersson

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=1145935045.3674.9.camel@localhost.localdomain \
    --to=dwalker@mvista.com \
    --cc=akpm@osdl.org \
    --cc=hzhong@gmail.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.