All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vijay Khemka <vijaykhemka@fb.com>
To: Samuel Mendoza-Jonas <sam@mendozajonas.com>,
	Joel Stanley <joel@jms.id.au>
Cc: "linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
	"OpenBMC Maillist" <openbmc@lists.ozlabs.org>,
	Sai Dasari <sdasari@fb.com>, "Amithash Prasad" <amithash@fb.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Justin.Lee1@Dell.com" <Justin.Lee1@Dell.com>
Subject: Re: [PATCH] net/ncsi: Add NCSI OEM command for FB Tiogapass
Date: Wed, 26 Sep 2018 17:07:43 +0000	[thread overview]
Message-ID: <FC2694E0-2F55-4089-8544-668243C6ECA2@fb.com> (raw)
In-Reply-To: <7cd8a49a057f1032e126b1e104fcf61e4956e06d.camel@mendozajonas.com>

>    Hi Vijay,
    
 >  Thanks for the patch; before I get too into a review though I'd like to
 >  loop in Justin (cc'd) who I know is also working on an OEM command patch.
 >  The changes here are very specific (eg. a command specific config option
 >  "CONFIG_NCSI_OEM_CMD_GET_MAC"), which is ok on a small scale but if we
 >  start to add an increasing amount of commands could get out of hand.
 >  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.
 >  It would be good to compare these two approaches first before committing
 >  to any one path
    
Hi Sam,
My oem command handler is generic and can be used for any oem commands and oem response handler can be made more generic. We can certainly write a wrapper to support netlink oem command to receive form user space. There are Mellanox specific functions which sends Mellanox specific request. These needed as a part of initial configuration. We can remove Kconfig option with more generic approach.

-Vijay 


  reply	other threads:[~2018-09-26 23:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  0:08 [PATCH] net/ncsi: Add NCSI OEM command for FB Tiogapass Vijay Khemka
2018-09-25  0:15 ` Vijay Khemka
2018-09-25  0:30 ` Joel Stanley
2018-09-25 18:16   ` Vijay Khemka
2018-09-26  4:33     ` Samuel Mendoza-Jonas
2018-09-26  4:33       ` Samuel Mendoza-Jonas
2018-09-26 17:07       ` Vijay Khemka [this message]
2018-09-26 18:07         ` Amithash Prasad
2018-09-26 20:39           ` Justin.Lee1
2018-09-27  3:20             ` Joel Stanley
2018-09-27  3:20               ` Joel Stanley
2018-09-27 17:46               ` Justin.Lee1
2018-09-27  3:43 ` Samuel Mendoza-Jonas
2018-09-27  3:54   ` Samuel Mendoza-Jonas
2018-09-28 22:26   ` Vijay Khemka

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=FC2694E0-2F55-4089-8544-668243C6ECA2@fb.com \
    --to=vijaykhemka@fb.com \
    --cc=Justin.Lee1@Dell.com \
    --cc=amithash@fb.com \
    --cc=joel@jms.id.au \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=sam@mendozajonas.com \
    --cc=sdasari@fb.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.