All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Spencer Ku (古世瑜)" <Spencer.Ku@quantatw.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: "Litzung Chen (陳利琮)" <Litzung.Chen@quantatw.com>,
	"Fran Hsu (徐誌謙)" <Fran.Hsu@quantatw.com>,
	"Nan Zhou" <nanzhou@google.com>
Subject: Implement Ethernet Interface Properties
Date: Wed, 1 Dec 2021 09:58:41 +0000	[thread overview]
Message-ID: <HK0PR04MB329947E4E37431B956A8D17AE4689@HK0PR04MB3299.apcprd04.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]

Hi All,



We want to implement two network Ethernet interface properties “Bandwidth” and “Drop package rate”, and expose the information via Redfish. The goal is that clients can talk to bmc via Redfish and get those two information. It will improve the debuggability of BMCs.



About the implement method, we divide the work into two parts: phosphor-network(or other suitable service) part, and bmcweb part.

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.



For bmcweb part, as I know so far, there has no suitable field under the EthernetInterface <https://redfish.dmtf.org/schemas/v1/EthernetInterface.v1_7_0.json> to set BW/Drop package rate. The idea is that read the value from D-bus then set the properties under the EthernetInterface OEM field. Please let me know if I have missed anything.



We are willing to see any suggestions and alternatives as well. Thanks!



Sincerely,

Spencer Ku

[-- Attachment #2: Type: text/html, Size: 4400 bytes --]

             reply	other threads:[~2021-12-01  9:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01  9:58 Spencer Ku (古世瑜) [this message]
2021-12-01 18:24 ` Implement Ethernet Interface Properties 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
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=HK0PR04MB329947E4E37431B956A8D17AE4689@HK0PR04MB3299.apcprd04.prod.outlook.com \
    --to=spencer.ku@quantatw.com \
    --cc=Fran.Hsu@quantatw.com \
    --cc=Litzung.Chen@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.