DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	"Cui, LunyuanX" <lunyuanx.cui@intel.com>,
	"Cui, LunyuanX" <lunyuanx.cui@intel.com>,
	"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/iavf: enable port reset
Date: Tue, 7 Apr 2020 01:37:41 +0000	[thread overview]
Message-ID: <9DEEADBC57E43F4DA73B571777FECECA41F21E13@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20200401071214.109641-1-lunyuanx.cui@intel.com>

Tested-by: Chen, Zhaoyan <zhaoyan.chen@intel.com>

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Lunyuan Cui
> Sent: Wednesday, April 1, 2020 3:12 PM
> To: dev@dpdk.org
> Cc: Yang, Qiming <qiming.yang@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Cui, LunyuanX <lunyuanx.cui@intel.com>
> Subject: [dpdk-dev] [PATCH v2] net/iavf: enable port reset
> 
> This patch is intended to add iavf_dev_reset ops, enable iavf to support
> "port reset all".
> 
> Signed-off-by: Lunyuan Cui <lunyuanx.cui@intel.com>
> Acked-by: Jingjing Wu <jingjing.wu@intel.com>
> ---
>  drivers/net/iavf/iavf_ethdev.c | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 
> diff --git a/drivers/net/iavf/iavf_ethdev.c b/drivers/net/iavf/iavf_ethdev.c
> index 7a8bec9c9..382530a43 100644
> --- a/drivers/net/iavf/iavf_ethdev.c
> +++ b/drivers/net/iavf/iavf_ethdev.c
> @@ -32,6 +32,7 @@ static int iavf_dev_configure(struct rte_eth_dev
> *dev);  static int iavf_dev_start(struct rte_eth_dev *dev);  static void
> iavf_dev_stop(struct rte_eth_dev *dev);  static void iavf_dev_close(struct
> rte_eth_dev *dev);
> +static int iavf_dev_reset(struct rte_eth_dev *dev);
>  static int iavf_dev_info_get(struct rte_eth_dev *dev,
>  			     struct rte_eth_dev_info *dev_info);  static
> const uint32_t *iavf_dev_supported_ptypes_get(struct rte_eth_dev *dev);
> @@ -91,6 +92,7 @@ static const struct eth_dev_ops iavf_eth_dev_ops = {
>  	.dev_start                  = iavf_dev_start,
>  	.dev_stop                   = iavf_dev_stop,
>  	.dev_close                  = iavf_dev_close,
> +	.dev_reset                  = iavf_dev_reset,
>  	.dev_infos_get              = iavf_dev_info_get,
>  	.dev_supported_ptypes_get   = iavf_dev_supported_ptypes_get,
>  	.link_update                = iavf_dev_link_update,
> @@ -1419,6 +1421,21 @@ iavf_dev_uninit(struct rte_eth_dev *dev)
>  	return 0;
>  }
> 
> +/*
> + * Reset VF device only to re-initialize resources in PMD layer  */
> +static int iavf_dev_reset(struct rte_eth_dev *dev) {
> +	int ret;
> +
> +	ret = iavf_dev_uninit(dev);
> +	if (ret)
> +		return ret;
> +
> +	return iavf_dev_init(dev);
> +}
> +
>  static int
>  iavf_dcf_cap_check_handler(__rte_unused const char *key,
>  			   const char *value, __rte_unused void *opaque)
> --
> 2.17.1


  reply	other threads:[~2020-04-07  1:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25  2:47 [dpdk-dev] [PATCH] " Lunyuan Cui
2020-03-26  3:26 ` Wu, Jingjing
2020-04-01  3:38 ` Ye Xiaolong
2020-04-01  7:12 ` [dpdk-dev] [PATCH v2] " Lunyuan Cui
2020-04-07  1:37   ` Chen, Zhaoyan [this message]
2020-04-08  6:47   ` Ye Xiaolong

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=9DEEADBC57E43F4DA73B571777FECECA41F21E13@SHSMSX104.ccr.corp.intel.com \
    --to=zhaoyan.chen@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=lunyuanx.cui@intel.com \
    --cc=qiming.yang@intel.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;
as well as URLs for NNTP newsgroup(s).