Skip to content

Dev/v0.5.34 verify#1007

Closed
zhanghaoyu1986 wants to merge 6 commits intokubewharf:mainfrom
zhanghaoyu1986:dev/v0.5.34-verify
Closed

Dev/v0.5.34 verify#1007
zhanghaoyu1986 wants to merge 6 commits intokubewharf:mainfrom
zhanghaoyu1986:dev/v0.5.34-verify

Conversation

@zhanghaoyu1986
Copy link
Copy Markdown
Collaborator

What type of PR is this?

Bug fixes/Enhancements

What this PR does / why we need it:

fix some corner cases and improve the robustness and versatility

…ue and irq

chore(irq-tuning): improve universality of getting mapping of nic queue
and irq

Signed-off-by: 张浩宇 <zhanghaoyu.zhy@bytedance.com>
…ent number of leading "0"

fix(irq-tuning): fix ComparesHexBitmapStrings two strings with different
number of leading "0" character.

Signed-off-by: 张浩宇 <zhanghaoyu.zhy@bytedance.com>
After setting the IRQ affinity for the kernel, the kernel cannot
guarantee that an immediate subsequent read will return the latest
value; in some cases, it may return an old value. This is because if
irq_do_set_affinity returns EBUSY, the kernel may call
irqd_set_move_pending to set the IRQD_SETAFFINITY_PENDING flag.
Subsequently, the next IRQ affinity write operation will set the newly
affinitized CPU mask into irq_desc->pending_mask.
At a later point, irq_move_masked_irq will clear the
IRQD_SETAFFINITY_PENDING flag within the interrupt context. The IRQ
affinity read function show_irq_affinity first reads
irq_desc->desc->irq_common_data.affinity and then checks whether the
IRQD_SETAFFINITY_PENDING flag is set. If the flag is set, it retrieves
irq_desc->pending_mask.
If the QRM read IRQ affinity syscall has already read
irq_desc->desc->irq_common_data.affinity but not yet read
irq_desc->pending_mask, and the interrupt context's irq_move_masked_irq
clears the IRQD_SETAFFINITY_PENDING flag at this point, QRM will end up
reading an old value.

Signed-off-by: 张浩宇 <zhanghaoyu.zhy@bytedance.com>
…rnel

report inconsistent irq affinity between qrm and kernel, this
inconsistence may caused by external services, like irqbalance-ng, or
manual set.

Signed-off-by: 张浩宇 <zhanghaoyu.zhy@bytedance.com>
chore(irq-tuning): ListNetNS ignores non-existed netns

Signed-off-by: 张浩宇 <zhanghaoyu.zhy@bytedance.com>
@zhanghaoyu1986 zhanghaoyu1986 added the workflow/need-review review: test succeeded, need to review label Oct 28, 2025
fix UT

Signed-off-by: 张浩宇 <zhanghaoyu.zhy@bytedance.com>
@codecov
Copy link
Copy Markdown

codecov Bot commented Oct 28, 2025

Codecov Report

❌ Patch coverage is 44.00000% with 70 lines in your changes missing coverage. Please review.
✅ Project coverage is 59.67%. Comparing base (85ac1d3) to head (0a14b61).
⚠️ Report is 5 commits behind head on main.

Files with missing lines Patch % Lines
...amicpolicy/irqtuner/controller/controller_linux.go 0.00% 35 Missing ⚠️
pkg/util/machine/network_linux.go 61.11% 29 Missing and 6 partials ⚠️

❌ Your patch status has failed because the patch coverage (44.00%) is below the target coverage (50.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1007      +/-   ##
==========================================
+ Coverage   58.68%   59.67%   +0.99%     
==========================================
  Files         679      682       +3     
  Lines       77274    63907   -13367     
==========================================
- Hits        45347    38136    -7211     
+ Misses      27540    21366    -6174     
- Partials     4387     4405      +18     
Flag Coverage Δ
unittest 59.67% <44.00%> (+0.99%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@JulyWindK JulyWindK closed this Oct 28, 2025
@JulyWindK JulyWindK removed the workflow/need-review review: test succeeded, need to review label Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants