From: Christian Ebner <c.ebner@proxmox.com>
To: Erik Fastermann <e.fastermann@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup v3] fix #7187: report: add ethtool output for physical interfaces
Date: Fri, 26 Jun 2026 11:06:04 +0200 [thread overview]
Message-ID: <9657d696-2bd6-4e0b-a067-fb4480dad7d3@proxmox.com> (raw)
In-Reply-To: <20260515083918.10590-1-e.fastermann@proxmox.com>
On 5/15/26 10:39 AM, Erik Fastermann wrote:
> Adding ethtool output to the report provides visibility into actual and
> supported NIC link speeds, making it much easier to diagnose network
> performance issues, negotiation failures, and configuration mismatches.
> It also reduces support back-and-forth.
>
Fixes: https://bugzilla.proxmox.com/show_bug.cgi?id=7187
although only the PBS part for this particular case.
> Signed-off-by: Erik Fastermann <e.fastermann@proxmox.com>
Reviewed-by: Christian Ebner <c.ebner@proxmox.com>
Tested-by: Christian Ebner <c.ebner@proxmox.com>
Code looks okay to me and this produces the expected output.
Only concern, although out of scope for this patch:
As noted in server/src/report.rs on the PDM side, code was basically
copied over from PBS for the initial implementation. The comment there
already suggest refactoring and splitting into a `proxmox-system-report`
crate.
It would make sense to do this sooner than later, as the reports are
likely to further diverge over time and code duplication to increase.
Could you tackle this as followup?
Maybe further split into product common commands (and files, ecc.) and
product specific commands (and files, ecc.). Product specific parts
could then maybe be defined as callbacks?
prev parent reply other threads:[~2026-06-26 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 8:39 [PATCH proxmox-backup v3] fix #7187: report: add ethtool output for physical interfaces Erik Fastermann
2026-06-09 6:39 ` Erik Fastermann
2026-06-26 9:06 ` Christian Ebner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9657d696-2bd6-4e0b-a067-fb4480dad7d3@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=e.fastermann@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.