DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Chengwen Feng <fengchengwen@huawei.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	 Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	dpdk-dev <dev@dpdk.org>,  Jingjing Wu <jingjing.wu@intel.com>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH] ethdev: modify comment of INTR RESET event
Date: Sat, 15 Jan 2022 12:14:12 +0530	[thread overview]
Message-ID: <CAH-L+nPHh4dqPFhDQcBmbHg2sWCeg4ZZUwe8XZq2qxbg6FBG7g@mail.gmail.com> (raw)
In-Reply-To: <5f36c0d0-3bce-ff70-d355-269686cad41a@intel.com>

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

Hi Ferruh,

Sorry for the late reply. Please see inline.

On Mon, Sep 27, 2021 at 9:49 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> On 7/26/2021 7:43 AM, Chengwen Feng wrote:
> > According to the definition of rte_eth_dev_reset(), the
> > RTE_ETH_EVENT_INTR_RESET event could also use when PF resets.
> >
>
> Can you please highlight the part in the 'rte_eth_dev_reset()' definition
> related to the RESET event usage for PF?
>
> > This patch modifies the comment of RTE_ETH_EVENT_INTR_RESET event, so
> > that it could use in all resets.
> >
>
> The original intention seems as the comment mentions, please check related
> commits [1].
>
> As far as I can get from below comments, usecase is,
> - PF sends reset command to VFs (driver internal command)
> - VF sends RESET event to application, to request reset to be performed by
> application.
>
> So event is more like a reset request from driver to application.
>
> Overall it is OK to extend the usage of the RESET event to PF, if there is
> a
> usecase for it. What is your usecase?
> And should we extend comment (API documentation) a little more to clarify
> when
> this even should be sent and what application should do when event
> received,
> what do you think?
>
> btw, cc'ed Ajit & Kales, as far as I remember in the past they suggest a
> recover
> event, maybe relevant with this discussion.
>
[Kalesh]: The recovery event we proposed was for a different purpose and
looks different from this.

In that case, PMD itself recovers from the FW error/reset conditions using
a handshaking protocol between PMD and the device FW without needing
application intervention.

I will send a new version of the patch set incorporating the comments I
received on the last version I had sent.

Regards,
Kalesh

>
>
>
> [1]
> Commit ae19955e7c86 ("i40evf: support reporting PF reset")
> Commit 514302ff6e00 ("ethdev: add NIC reset operation")
>
> > Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
> > ---
> >  lib/ethdev/rte_ethdev.h | 3 +--
> >  1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h
> > index d2b27c3..e6646a6 100644
> > --- a/lib/ethdev/rte_ethdev.h
> > +++ b/lib/ethdev/rte_ethdev.h
> > @@ -3499,8 +3499,7 @@ enum rte_eth_event_type {
> >       RTE_ETH_EVENT_INTR_LSC, /**< lsc interrupt event */
> >       RTE_ETH_EVENT_QUEUE_STATE,
> >                               /**< queue state event (enabled/disabled)
> */
> > -     RTE_ETH_EVENT_INTR_RESET,
> > -                     /**< reset interrupt event, sent to VF on PF reset
> */
> > +     RTE_ETH_EVENT_INTR_RESET, /**< reset interrupt event */
> >       RTE_ETH_EVENT_VF_MBOX,  /**< message from the VF received by PF */
> >       RTE_ETH_EVENT_MACSEC,   /**< MACsec offload related event */
> >       RTE_ETH_EVENT_INTR_RMV, /**< device removal event */
> >
>
>

-- 
Regards,
Kalesh A P

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

      reply	other threads:[~2022-01-15  6:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26  6:43 Chengwen Feng
2021-08-11  7:15 ` Singh, Aman Deep
2021-09-27 16:19 ` Ferruh Yigit
2022-01-15  6:44   ` Kalesh Anakkur Purayil [this message]

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=CAH-L+nPHh4dqPFhDQcBmbHg2sWCeg4ZZUwe8XZq2qxbg6FBG7g@mail.gmail.com \
    --to=kalesh-anakkur.purayil@broadcom.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=thomas@monjalon.net \
    /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;
as well as URLs for NNTP newsgroup(s).