drivers/net: setting loopback network driver sending task to the HPWORK queue #17597
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ueue The loopback network driver sending task is placed in the LPWORK queue, which may result in delayed scheduling when the CPU usage reaches 100%, leading to the timely sending of cached messages from the loopback network driver and causing issues with post waitsem being too late.we decied to set loopback sending task to the HPWORK queue. Signed-off-by: wangchen <wangchen41@xiaomi.com>
wangchen61698
requested review from
jerpelea and
xiaoxiang781216
as code owners
github-actions
bot
added
Area: Networking
acassis
approved these changes
Dec 22, 2025
Contributor
acassis
left a comment
acassis
left a comment
There was a problem hiding this comment.
@wangchen61698 is there some possibility to happen the opposite: the loopback interface be used to starving the system? It could be used for some DoS (Denial of Service) attack to render IoT devices unusable in the field.
jerpelea
changed the title
jerpelea
approved these changes
Dec 22, 2025
Contributor
jerpelea
left a comment
jerpelea
left a comment
There was a problem hiding this comment.
please update the commit title to
drivers/net: setting loopback network driver sending task to the HPWORK queue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: Please adhere to Contributing Guidelines.
Summary
The loopback network driver sending task is placed in the LPWORK queue, which may result in delayed scheduling when the CPU usage reaches 100%, leading to the timely sending of cached messages from the loopback network driver and causing issues with post waitsem being too late.we decied to set loopback sending task to the HPWORK queue.
Impact
loopback
Testing
It has passed self-testing in true machine(speaker equipment)