Details
-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
17290
Description
At the recent developers conference, Jinshan proposed a different method of approaching the performance problems described in LU-6148.
Instead of introducing a new type of LDLM lock matching, we'd like to make it possible for user space to explicitly request LDLM locks asynchronously from the IO.
I've implemented a prototype version of the feature and will be uploading it for comments. I'll explain the state of the current version in a comment momentarily.
Attachments
Issue Links
- is blocking
-
LU-9962 Possible file size glimpse issue
-
- Resolved
-
- is related to
-
LU-10136 sanity test_255c: Ladvise test11 failed, 255
-
- Resolved
-
-
LUDOC-379 Document ladvise lockahead feature
-
- Resolved
-
-
LU-6181 Fix lock contention discovery to disable extend lock growth
-
- Closed
-
-
LU-11618 implement ladvise rpc_size for optimized performance
-
- Open
-
-
LU-6148 Strided lock proposal - Feature proposal for 2.8
-
- Resolved
-
- is related to
-
LU-7225 change ladvise wire protocol for lockahead and future usage
-
- Resolved
-
Activity
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Parent |
Original:
|
|
Issue Type | Original: Technical task [ 7 ] | New: New Feature [ 2 ] |
Attachment | Original: LockAheadResults.docx [ 26841 ] |
Attachment | New: LockAheadResults.docx [ 26927 ] |
Attachment | New: cug paper.pdf [ 26925 ] | |
Attachment | New: mmoore cug slides.pdf [ 26926 ] |