From: Patrick Williams <patrick@stwcx.xyz>
To: "Spencer Ku (古世瑜)" <Spencer.Ku@quantatw.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"Fran Hsu (徐誌謙)" <Fran.Hsu@quantatw.com>,
"Litzung Chen (陳利琮)" <Litzung.Chen@quantatw.com>,
"Nan Zhou" <nanzhou@google.com>
Subject: Re: Implement Ethernet Interface Properties
Date: Wed, 1 Dec 2021 16:49:52 -0600 [thread overview]
Message-ID: <Yaf8EOu4qSY10q87@heinlein> (raw)
In-Reply-To: <HK0PR04MB329947E4E37431B956A8D17AE4689@HK0PR04MB3299.apcprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
On Wed, Dec 01, 2021 at 09:58:41AM +0000, Spencer Ku (古世瑜) wrote:
> For phosphor-network part, we propose to use existing tool like ipert to get the Ethernet BW/Drop package rate. Or the other method is that read TX/RX from ethernet driver (/sys/class/net/{Ethernet_Name}), then calculate the BW/Drop package rate. After that, we will need to register the D-Bus interface and sync the property info to that D-Bus.
Is this something that systemd-networkd might be interested in exposing? We
should ask this question upstream there to see if they would be interested in
the contribution.
I'd prefer using the sysfs interface direction rather than wrapping a tool in
`system()` calls.
Did you mean 'iperf'? How do you get the drop rate from that? Don't you need
another system to act as the other side of iperf?
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-12-01 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 9:58 Implement Ethernet Interface Properties Spencer Ku (古世瑜)
2021-12-01 18:24 ` Ed Tanous
2021-12-02 8:45 ` Spencer Ku (古世瑜)
2022-01-20 8:42 ` Spencer Ku (古世瑜)
2022-01-20 9:07 ` i.kononenko
2022-01-24 2:22 ` Spencer Ku (古世瑜)
2022-01-24 20:37 ` Ed Tanous
2022-01-25 8:00 ` Spencer Ku (古世瑜)
2021-12-01 22:49 ` Patrick Williams [this message]
2021-12-02 9:22 ` Spencer Ku (古世瑜)
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=Yaf8EOu4qSY10q87@heinlein \
--to=patrick@stwcx.xyz \
--cc=Fran.Hsu@quantatw.com \
--cc=Litzung.Chen@quantatw.com \
--cc=Spencer.Ku@quantatw.com \
--cc=nanzhou@google.com \
--cc=openbmc@lists.ozlabs.org \
/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.