-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cherry-pick volatile branch to release 1.0 of main branch #348
Conversation
Signed-off-by: Yu, Peng <peng.yu@intel.com>
Signed-off-by: Jiayu Wu <jiayu.wu@intel.com>
Signed-off-by: Jiayu Wu <jiayu.wu@intel.com>
Signed-off-by: Jiayu Wu <jiayu.wu@intel.com>
engine/allocator.hpp
Outdated
@@ -192,8 +180,7 @@ class Allocator { | |||
uint64_t max_offset_; | |||
|
|||
bool thread_local_counter_enabled_{}; | |||
uint32_t num_thread_local_counters{0}; | |||
std::int64_t* thread_allocated_sizes_{nullptr}; | |||
std::vector<int64_t> thread_allocated_sizes_{}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
std::vector
is supposed to have potential bottleneck here. This was discussed before : #329 (review)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think std::int64* would resolve this problem, we need to align it to cache line
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK. I misunderstood this problem.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will you do the alignment in this pull request?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
What is changed and how it works?
Cherry-pick volatile branch to release 1.0 of main branch
Check List
Tests