From: Scott Branden <scott.branden@broadcom.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "David S. Miller" <davem@davemloft.net>,
"Allan W. Nielsen" <allan.nielsen@microsemi.com>,
Raju Lakkaraju <Raju.Lakkaraju@microsemi.com>,
Florian Fainelli <f.fainelli@gmail.com>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
linux-kernel@vger.kernel.org,
Steve Lin <steven.lin1@broadcom.com>
Subject: Re: [PATCH 0/1] net: ethtool: add SmartNIC reset support
Date: Wed, 18 Oct 2017 09:52:29 -0700 [thread overview]
Message-ID: <b9f6864a-e746-bb0d-ec8f-b85924276266@broadcom.com> (raw)
In-Reply-To: <20171018162823.GB15371@lunn.ch>
Hi Andrew,
On 17-10-18 09:28 AM, Andrew Lunn wrote:
> On Wed, Oct 18, 2017 at 09:01:35AM -0700, Scott Branden wrote:
>> Ethtool provides support for resetting other internal portions of the
>> NIC already. Seems appropriate to use one of the bits for resetting
>> the application processor (AP) for SmartNICs.
> Hi Scott
>
> Do you also have a management processor on the NIC?
>
> Or is the Application Processor just the Marketing Departments name
> for the management processor?
Yes, there is also a management processor.
In our next gen SmartNIC the "Application processor" may actually
have 8 very powerful cores.
But, if they need to be reset, we reset them all.
>
> Andrew
next prev parent reply other threads:[~2017-10-18 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 16:01 Scott Branden
2017-10-18 16:01 ` [PATCH 1/1] net: ethtool: add support for reset of AP inside NIC interface Scott Branden
2017-10-18 21:59 ` Scott Branden
2017-10-18 16:28 ` [PATCH 0/1] net: ethtool: add SmartNIC reset support Andrew Lunn
2017-10-18 16:52 ` Scott Branden [this message]
2017-10-18 19:16 ` Andrew Lunn
2017-10-18 19:31 ` Scott Branden
2017-10-18 21:30 ` Andy Gospodarek
2017-10-18 21:59 ` Scott Branden
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=b9f6864a-e746-bb0d-ec8f-b85924276266@broadcom.com \
--to=scott.branden@broadcom.com \
--cc=Raju.Lakkaraju@microsemi.com \
--cc=allan.nielsen@microsemi.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steven.lin1@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®