OpenBLAS controlling thread logic needs to be smarter when thre are overlapping set/restore pairs in different threads

未关闭
#299 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@itamarst 已经在做这个了。

开始于 2026年11月5日。

  • #300 来自 @itamarst —— 未关闭

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
performance

调研方向

Start with the linked pull request #300 and the thread-limit set/restore logic it discusses. Trace how control ownership and saved limits behave in the two-thread scenario described in the issue. Done means a thread that failed to set a limit cannot later restore one and acquire control unexpectedly; verify the behavior with a regression test for the overlapping pairs.

由索引模型根据 Issue 内容生成。

描述

Based on https://github.com/joblib/joblib/pull/1871#issuecomment-6663799616

Scenario:

  1. Initial limit is L.
  2. Thread 1 limits to M, stores the fact that previously limit was L. Thread 1 becomes controlling thread.
  3. Thread 2 tries to limit to N, but fails, stores the fact that previously limit was M.
  4. Thread 1 restores to L and releases control of thread.
  5. Thread 2 restores to N, acquiring control as it does so.

The straightforward solution here is something like "if a thread failed to set because it wasn't the controlling thread, it shouldn't restore either."

主要语言
Python
星标
434
派生
38
平均合并
1 天 4 小时
30 天内合并 PR
18

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

joblib/threadpoolctl 的其他 Issue

查看 joblib/threadpoolctl 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。