From: Jiri Pirko <jiri@resnulli.us>
To: Vasundhara Volam <vasundhara-v.volam@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
michael.chan@broadcom.com, kuba@kernel.org, jiri@mellanox.com,
moshe@mellanox.com, ayal@mellanox.com, parav@mellanox.com
Subject: Re: [RFC net-next] devlink: Add reset subcommand.
Date: Mon, 29 Jun 2020 15:51:34 +0200 [thread overview]
Message-ID: <20200629135134.GA2227@nanopsycho.orion> (raw)
In-Reply-To: <1592911969-10611-1-git-send-email-vasundhara-v.volam@broadcom.com>
Tue, Jun 23, 2020 at 01:32:49PM CEST, vasundhara-v.volam@broadcom.com wrote:
>Advanced NICs support live reset of some of the hardware
>components, that resets the device immediately with all the
>host drivers loaded.
>
>Add devlink reset subcommand to support live and deferred modes
>of reset. It allows to reset the hardware components of the
>entire device and supports the following fields:
>
>component:
>----------
>1. MGMT : Management processor.
>2. IRA : Interrupt requester.
>3. DMA : DMA engine.
>4. FILTER : Filtering/flow direction.
>5. OFFLOAD : Protocol offload.
>6. MAC : Media access controller.
>7. PHY : Transceiver/PHY.
Hmm. I think that you are mixing things which are per-ASIC and per-port.
It is confusing.
Why do you need this kind of reset granularity? I mean, if something
goes wrong in fw/hw, the health reporter should report it and recover
it. This looks like you try to add another interface for the same set of
problem...
>8. RAM : RAM shared between multiple components.
>9. ROCE : RoCE management processor.
>10. AP : Application processor.
>11. All : All possible components.
>
>Drivers are allowed to reset only a subset of requested components.
>
>width:
>------
>1. single - Single function.
>2. multi - Multiple functions.
>
>mode:
>-----
>1. deferred - Reset will happen after unloading all the host drivers
> on the device. This is be default reset type, if user
> does not specify the type.
>2. live - Reset will happen immediately with all host drivers loaded
> in real time. If the live reset is not supported, driver
> will return the error.
>
>This patch is a proposal in continuation to discussion to the
>following thread:
>
>"[PATCH v3 net-next 0/6] bnxt_en: Add 'enable_live_dev_reset' and 'allow_live_dev_reset' generic devlink params."
>
>and here is the URL to the patch series:
>
>https://patchwork.ozlabs.org/project/netdev/list/?series=180426&state=*
>
>If the proposal looks good, I will re-send the whole patchset
>including devlink changes and driver usage.
>
[...]
next prev parent reply other threads:[~2020-06-29 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 11:32 [RFC net-next] devlink: Add reset subcommand Vasundhara Volam
2020-06-23 20:56 ` Michal Kubecek
2020-06-24 4:44 ` Vasundhara Volam
2020-06-29 13:51 ` Jiri Pirko [this message]
2020-06-29 14:57 ` Vasundhara Volam
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=20200629135134.GA2227@nanopsycho.orion \
--to=jiri@resnulli.us \
--cc=ayal@mellanox.com \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=parav@mellanox.com \
--cc=vasundhara-v.volam@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