mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: tom.leiming@gmail.com
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	mingo@elte.hu, torvalds@linux-foundation.org
Subject: Re: [tip:core/locking 2/3] lockdep:define preallocated "stack" for BFS as per cpu variable
Date: Wed, 22 Jul 2009 15:03:50 +0200	[thread overview]
Message-ID: <1248267830.27058.1404.camel@twins> (raw)
In-Reply-To: <1248267513-4934-3-git-send-email-tom.leiming@gmail.com>

On Wed, 2009-07-22 at 20:58 +0800, tom.leiming@gmail.com wrote:
> From: Ming Lei <tom.leiming@gmail.com>

This patch can use a changelog.

Why is this needed, isn't all that serialized by the graph_lock anyway?
Or are there a few paths where this isn't the case and we're now racy?

> Signed-off-by: Ming Lei <tom.leiming@gmail.com>
> ---
>  kernel/lockdep.c |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/lockdep.c b/kernel/lockdep.c
> index 1b1796a..1583439 100644
> --- a/kernel/lockdep.c
> +++ b/kernel/lockdep.c
> @@ -847,7 +847,7 @@ struct circular_queue {
>  	unsigned int  front, rear;
>  };
>  
> -static struct circular_queue lock_cq;
> +static DEFINE_PER_CPU(struct circular_queue, lock_cq);
>  
>  unsigned int max_bfs_queue_depth;
>  
> @@ -937,7 +937,7 @@ static int __bfs(struct lock_list *source_entry,
>  {
>  	struct lock_list *entry;
>  	struct list_head *head;
> -	struct circular_queue *cq = &lock_cq;
> +	struct circular_queue *cq = &get_cpu_var(lock_cq);
>  	int ret = 1;
>  
>  	if (match(source_entry, data)) {
> @@ -993,6 +993,7 @@ static int __bfs(struct lock_list *source_entry,
>  		}
>  	}
>  exit:
> +	put_cpu_var(lock_cq);
>  	return ret;
>  }
>  


  parent reply	other threads:[~2009-07-22 13:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 12:58 [tip:core/locking 0/3] lockdep:bfs optimization tom.leiming
2009-07-22 12:58 ` [tip:core/locking 1/3] lockdep:reintroduce generation count to make BFS faster tom.leiming
2009-07-22 12:58   ` [tip:core/locking 2/3] lockdep:define preallocated "stack" for BFS as per cpu variable tom.leiming
2009-07-22 12:58     ` [tip:core/locking 3/3] lockdep:add likely/unlikely annotations to BFS core routine tom.leiming
2009-07-22 13:06       ` Peter Zijlstra
2009-07-22 13:03     ` Peter Zijlstra [this message]
2009-07-22 13:10       ` [tip:core/locking 2/3] lockdep:define preallocated "stack" for BFS as per cpu variable Ming Lei
2009-07-22 13:19         ` Peter Zijlstra
2009-07-22 13:45           ` Ming Lei
2009-07-22 13:04   ` [tip:core/locking 1/3] lockdep:reintroduce generation count to make BFS faster Peter Zijlstra
2009-07-22 13:17     ` Ming Lei

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=1248267830.27058.1404.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tom.leiming@gmail.com \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®