summaryrefslogtreecommitdiff
path: root/src/mongo/db/d_concurrency.h
diff options
context:
space:
mode:
authorAndy Schwerin <schwerin@10gen.com>2012-03-16 22:05:39 -0400
committerAndy Schwerin <schwerin@10gen.com>2012-03-16 22:05:39 -0400
commitb8cec6e3c0df43c63e096dabd93d5697c6143b82 (patch)
tree3179d5fa375fc8440ad90b4b872fa92ed8b0d31e /src/mongo/db/d_concurrency.h
parent938ac1619dc88dc5f9e6df47dcb981fbf0f33663 (diff)
downloadmongo-b8cec6e3c0df43c63e096dabd93d5697c6143b82.tar.gz
Roll back most of the following two patches:
c4851043c682c9e2a9230166045ce85b518b85eb: qlock can ask if in greedy mode or not 938ac1619dc88dc5f9e6df47dcb981fbf0f33663: if in ThreadSpanningOp don't profile The problem is that isGreedSuspended cannot be called with the qlock's internal mutex already held. However, a caller not holding that lock already can't know that by the time the function returns, its return value is still valid. Another thread may change it in parallel. The result is that the attempt to use it to stop profiling when thread-spanning ops are enabled only appears to provide that protection.
Diffstat (limited to 'src/mongo/db/d_concurrency.h')
-rw-r--r--src/mongo/db/d_concurrency.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/src/mongo/db/d_concurrency.h b/src/mongo/db/d_concurrency.h
index 06b62dd1027..085f5775fec 100644
--- a/src/mongo/db/d_concurrency.h
+++ b/src/mongo/db/d_concurrency.h
@@ -77,7 +77,6 @@ namespace mongo {
static void W_to_R();
static void unsetW(); // reverts to greedy
static void unsetR(); // reverts to greedy
- static bool isEnabled(); // if the thread spanning lock is enabled
};
};