Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mariadb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
mariadb
Commits
cf0acb16
Commit
cf0acb16
authored
Apr 17, 2013
by
Zardosht Kasheff
Committed by
Yoni Fogel
Apr 17, 2013
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[t:4431], add comments
git-svn-id:
file:///svn/toku/tokudb@42767
c7de825b-a66e-492c-adef-691d508d4ae1
parent
865b81d0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
9 deletions
+10
-9
newbrt/brt-cachetable-wrappers.h
newbrt/brt-cachetable-wrappers.h
+10
-9
No files found.
newbrt/brt-cachetable-wrappers.h
View file @
cf0acb16
...
...
@@ -53,11 +53,11 @@ toku_create_new_brtnode (
);
/**
*
The intent of toku_pin_brtnode(_holding_lock) is to abstract th
e
*
process of retrieving a node from the rest of brt.c, so that there is
* o
nly one place where we need to worry applying ancestor messages to a
*
leaf node. The idea is for all of brt.c (search, splits, merges,
*
flushes, etc) to access a node via toku_pin_brtnode(_holding_lock)
*
toku_pin_brtnode either pins a brtnode, if the operation is fast (becaus
e
*
a partial fetch is not required and there is no contention for the node)
* o
r it returns TOKUDB_TRY_AGAIN after unlocking its ancestors (using
*
unlockers and ancestors) and bringing the necessary pieces of the node
*
into memory.
*/
int
toku_pin_brtnode
(
...
...
@@ -75,10 +75,11 @@ toku_pin_brtnode(
);
/**
* Pin a brtnode off the client thread, which means
* it is pinned without the ydb lock being held.
* As a result, unlike toku_pin_brtnode, we cannot apply ancestor
* messages.
* Unfortunately, this function is poorly named
* as over time, client threads have also started
* calling this function.
* This function returns a pinned brtnode to the caller.
* Unlike toku_pin_brtnode, this function blocks until the node is pinned.
*/
void
toku_pin_brtnode_off_client_thread
(
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment