[PATCH] net/ncsi: Add NCSI OEM command for FB Tiogapass
joel at jms.id.au
Thu Sep 27 13:20:07 AEST 2018
On Thu, 27 Sep 2018 at 00:39, <Justin.Lee1 at dell.com> wrote:
> > > As I understand Justin's version adds a generic handler, using the NCSI
> > > Netlink interface to pass OEM commands and responses to and from
> > > userspace, which does the actual packet handling.
> > Thanks for the direction Sam! Justin, if you don't mind, can you share the patches you have to add the support? This actually would solve a few other things we are trying to accomplish.
> Basically, I add a new flag to indicate the request is coming from the Netlink interface to allow the command handler and response handler to react.
> #define NCSI_REQ_FLAG_NETLINK_DRIVEN 2
> The work flow is as below.
> User space application -> Netlink interface (msg) -> new Netlink handler - ncsi_send_cmd_nl() - ncsi_xmit_cmd()
> Response received - ncsi_rcv_rsp() -> internal response handler - ncsi_rsp_handler_xxx() -> ncsi_send_netlink_rsp () -> Netlink interface (msg) -> user space application
> Command timeout - ncsi_request_timeout() -> ncsi_send_netlink_timeout () -> Netlink interface (msg with zero data length) -> user space application
> Detected error -> ncsi_send_netlink_err () -> Netlink interface (err msg) -> user space application
> I will clean up some code and send out the patch.
Thanks for the overview. We look forward to your patches; please
include the same cc list as this series.
I think it makes sense to have some OEM NCSI handing purely in the
kenrel. This would allow eg. the MAC address of an interface to be
correct at boot, without requiring userspace to come up first.
I have also heard stories of temperature sensors over NCSI. Those
would make sense to be hwmon drivers, which again would mean handling
them in the kernel.
Justin, Vijay, can you please list the known NCSI OEM
commands/extensions that we plan on implementing?
More information about the openbmc