-
Notifications
You must be signed in to change notification settings - Fork 10
[SIG-CLOUD-9] LE-3923 LE-3919 LE-3915 #549
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
[SIG-CLOUD-9] LE-3923 LE-3919 LE-3915 #549
Conversation
…htool. jira LE-3915 commit-author Dipayaan Roy <[email protected]> commit c09ef59 Add support for reporting additional hardware counters for drop and TC using the ethtool -S interface. These counters include: - Aggregate Rx/Tx drop counters - Per-TC Rx/Tx packet counters - Per-TC Rx/Tx byte counters - Per-TC Rx/Tx pause frame counters The counters are exposed using ethtool_ops->get_ethtool_stats and ethtool_ops->get_strings. This feature/counters are not available to all versions of hardware. Signed-off-by: Dipayaan Roy <[email protected]> Reviewed-by: Subbaraya Sundeep <[email protected]> Reviewed-by: Haiyang Zhang <[email protected]> Link: https://patch.msgid.link/20250609100103.GA7102@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net Signed-off-by: Jakub Kicinski <[email protected]> (cherry picked from commit c09ef59) Signed-off-by: Shreeya Patel <[email protected]>
jira LE-3919 commit-author Haiyang Zhang <[email protected]> commit 7768c5f To collaborate with hardware servicing events, upon receiving the special EQE notification from the HW channel, remove the devices on this bus. Then, after a waiting period based on the device specs, rescan the parent bus to recover the devices. Signed-off-by: Haiyang Zhang <[email protected]> Reviewed-by: Shradha Gupta <[email protected]> Reviewed-by: Simon Horman <[email protected]> Link: https://patch.msgid.link/[email protected] Signed-off-by: Jakub Kicinski <[email protected]> (cherry picked from commit 7768c5f) Signed-off-by: Shreeya Patel <[email protected]>
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.
Seems like you may have picked up a couple of lines accidently in one patch (commented)
if (err || resp->status) { | ||
if (req->req.msg_type != MANA_QUERY_PHY_STAT) | ||
if (err == -EOPNOTSUPP) | ||
return err; |
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.
Was adding these two lines intentional? I don't think they are part of this changeset
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.
hmm I added them because of the conflict caused due to missing this patch ca8ac48
I tried to add that patch but it was causing more conflicts so I ended up adding just these two lines. Now I am thinking maybe I should just drop these lines instead?
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.
I don't think these two lines hurt anything, but it feels like they don't belong with this changeset. I think I'd remove them.
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.
what where the conflicts this seems pretty valid if the underlaying hardware isn't supported it would error out and the code doesn't' seem super complex ...
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.
@PlaidCat @bmastbergen conflicts were related to mana_query_link_cfg
and mana_set_bw_clamp
function since these functions are not present in the current SCN 9/10 kernel, patch ca8ac48 failed to apply cleanly. So what I did was to just add the part of that patch to this mana_send_request
function.
@PlaidCat Brett mentioned to remove this part as it is not related to this changeset. What is your suggestion?
I'm okay with either of the options
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.
lets do what @bmastbergen suggested
We could probably do the backport and just exclude the missing stuff.
HOWEVER we might want to cut a ticket as that commit you referenced seems like a good patch-set to provide in future releases
https://lore.kernel.org/all/[email protected]/
jira LE-3923 commit-author Haiyang Zhang <[email protected]> commit fbe346c upstream-diff There were conflicts seen when applying this patch due to the following missing commits :- ca8ac48 ("net: mana: Handle unsupported HWC commands") 505cc26 ("net: mana: Add support for auxiliary device servicing events") Upon receiving the Reset Request, pause the connection and clean up queues, wait for the specified period, then resume the NIC. In the cleanup phase, the HWC is no longer responding, so set hwc_timeout to zero to skip waiting on the response. Signed-off-by: Haiyang Zhang <[email protected]> Link: https://patch.msgid.link/[email protected] Signed-off-by: Jakub Kicinski <[email protected]> (cherry picked from commit fbe346c) Signed-off-by: Shreeya Patel <[email protected]>
784a7bf
to
2dc9cfa
Compare
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.
🥌
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.
7e4fcbb
into
sig-cloud-9/5.14.0-570.33.2.el9_6
Commit Messages
Kernel Build
kernel-build.log
Kselftest
kselftest-after.log
kselftest-before.log
Testing