feat: allow running a poller on custom thread (backport #98)#99
feat: allow running a poller on custom thread (backport #98)#99mergify[bot] merged 2 commits intodevelopfrom
Conversation
This is a monotonic increasing id which begins at 1 and is used to identify threads. This id cannot overflow... a restart would be required. Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com> (cherry picked from commit e88f558)
This required refactoring the selection to add for 3 options: 1. current thread 2. new thread on specified core 3. explicitly specified thread This is useful as it allows us to run pollers on existing threads to avoid running down the thread message pool. Specifically for nvmx, rather than create a thread per replica, we'd now be able to share threads on each core per replica. Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com> (cherry picked from commit 1111cd8)
|
Cherry-pick of 9664a7f has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
openebs-ci
left a comment
There was a problem hiding this comment.
Automatically approved backport PR
🧪 CI InsightsHere's what we observed from your CI run for e1be4fa. 🟢 All jobs passed!But CI Insights is watching 👀 |
543806b to
e1be4fa
Compare
|
@mergify queue |
Merge Queue Status
This pull request spent 5 seconds in the queue, including 1 second running CI. Required conditions to merge
ReasonPull request #99 has been dequeued, merge conditions unmatch:
HintYou should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it. |
|
@mergify requeue |
Merge Queue Status
This pull request spent 11 seconds in the queue, including 1 second running CI. Required conditions to merge
|
This is an automatic backport of pull request #98 done by [Mergify](https://mergify.com).