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 1/3] lockdep:reintroduce generation count to make BFS faster
Date: Wed, 22 Jul 2009 15:04:58 +0200 [thread overview]
Message-ID: <1248267898.27058.1407.camel@twins> (raw)
In-Reply-To: <1248267513-4934-2-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>
>
> We still can apply DaveM's generation count optimization to
> BFS, so reintroduce it.
Please elaborate, changelogs are important.
You fail to explain why it still applies and what the gains are.
(I can guess, but you explaining makes sure we're on the same page)
next prev parent reply other threads:[~2009-07-22 13:03 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 ` [tip:core/locking 2/3] lockdep:define preallocated "stack" for BFS as per cpu variable Peter Zijlstra
2009-07-22 13:10 ` Ming Lei
2009-07-22 13:19 ` Peter Zijlstra
2009-07-22 13:45 ` Ming Lei
2009-07-22 13:04 ` Peter Zijlstra [this message]
2009-07-22 13:17 ` [tip:core/locking 1/3] lockdep:reintroduce generation count to make BFS faster 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=1248267898.27058.1407.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®