From: tom.leiming@gmail.com
To: a.p.zijlstra@chello.nl
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mingo@elte.hu, torvalds@linux-foundation.org,
Ming Lei <tom.leiming@gmail.com>
Subject: [tip:core/locking 0/3] lockdep:bfs optimization
Date: Wed, 22 Jul 2009 20:58:30 +0800 [thread overview]
Message-ID: <1248267513-4934-1-git-send-email-tom.leiming@gmail.com> (raw)
From: Ming Lei <tom.leiming@gmail.com>
This series does the BFS optimizations:
.reintroduce DaveM's generation id to bfs to make it faster
.make bfs preallocated "stack" as per cpu variable
.add likely/unlikely annotations to BFS core routine
and the patches are based on Peter's patches against tip:core/locking:
http://marc.info/?l=linux-kernel&m=124793787804558&w=2
http://marc.info/?l=linux-kernel&m=124793787804556&w=2
Also, the patches have passed lockdep's selftest.
include/linux/lockdep.h | 1 +
kernel/lockdep.c | 26 ++++++++++++++------------
2 files changed, 15 insertions(+), 12 deletions(-)
Thanks,
Lei Ming
next reply other threads:[~2009-07-22 12:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 12:58 tom.leiming [this message]
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 ` [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=1248267513-4934-1-git-send-email-tom.leiming@gmail.com \
--to=tom.leiming@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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®