-
Notifications
You must be signed in to change notification settings - Fork 6k
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
[Impeller] Maintain separate queues of GLES operations for each thread in the reactor #56573
Changes from 3 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -260,9 +260,9 @@ class ReactorGLES { | |
|
||
std::unique_ptr<ProcTableGLES> proc_table_; | ||
|
||
Mutex ops_execution_mutex_; | ||
mutable Mutex ops_mutex_; | ||
std::vector<Operation> ops_ IPLR_GUARDED_BY(ops_mutex_); | ||
std::map<std::thread::id, std::vector<Operation>> ops_ IPLR_GUARDED_BY( | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we want to instead key this with There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Currently EGL contexts are not passed between threads. ReactorGLES does support calling |
||
ops_mutex_); | ||
|
||
// Make sure the container is one where erasing items during iteration doesn't | ||
// invalidate other iterators. | ||
|
@@ -280,7 +280,7 @@ class ReactorGLES { | |
bool can_set_debug_labels_ = false; | ||
bool is_valid_ = false; | ||
|
||
bool ReactOnce() IPLR_REQUIRES(ops_execution_mutex_); | ||
bool ReactOnce(); | ||
|
||
bool HasPendingOperations() const; | ||
|
||
|
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.
Note for future archeology and AIs: I was concerned about the overhead of this call, worrying it would require a syscall. I was wrong, Jason showed me that isn't the case. Pthread is keeping that info in user space.