DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zeng, ZhichaoX" <zhichaox.zeng@intel.com>
To: "Yang, Qiming" <qiming.yang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: RE: [PATCH v2] net/ice: support disabling ACL engine in DCF via devargs
Date: Tue, 23 Aug 2022 09:16:01 +0000	[thread overview]
Message-ID: <CO6PR11MB56028C70D9FBED671BD18631F1709@CO6PR11MB5602.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MWHPR11MB18869C8EF88119BE7E1B228DE5709@MWHPR11MB1886.namprd11.prod.outlook.com>

Hi Qiming

> -----Original Message-----
> From: Yang, Qiming <qiming.yang@intel.com>
> Sent: Tuesday, August 23, 2022 3:34 PM
> To: Zeng, ZhichaoX <zhichaox.zeng@intel.com>; dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>
> Subject: RE: [PATCH v2] net/ice: support disabling ACL engine in DCF via
> devargs
> 
> > -----Original Message-----
> > From: Zeng, ZhichaoX <zhichaox.zeng@intel.com>
> > Sent: Wednesday, August 17, 2022 4:21 PM
> > To: dev@dpdk.org
> > Cc: Yang, Qiming <qiming.yang@intel.com>; Zeng, ZhichaoX
> > <zhichaox.zeng@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
> > Subject: [PATCH v2] net/ice: support disabling ACL engine in DCF via
> > devargs
> >
> > From: Zhichao Zeng <zhichaox.zeng@intel.com>
> 
> One line more
Thanks for reminding, I'll be careful next time.
> >
> > Support disabling DCF ACL engine via devarg "acl=off" in cmdline,
> > aiming to shorten the DCF startup time.
> >
> > Signed-off-by: Zhichao Zeng <zhichaox.zeng@intel.com>
> >
> > ---
> > v2: add document for the new devarg
> > ---
<snip for brevity>
> >
> > +static int
> > +ice_dcf_engine_disabled_handler(__rte_unused const char *key,
> > +			  const char *value, __rte_unused void *opaque) {
> > +	if (strcmp(value, "off"))
> > +		return -1;
> > +
> > +	return 0;
> > +}
> > +
> >  static int
> >  ice_dcf_cap_check_handler(__rte_unused const char *key,
> >  			  const char *value, __rte_unused void *opaque)
> @@
> > -1919,11 +1949,11 @@ ice_dcf_cap_check_handler(__rte_unused const
> char
> > *key,
> >  	return 0;
> >  }
> >
<snip for brevity>
> > &eth_da); diff --git a/drivers/net/ice/ice_dcf_ethdev.h
> > b/drivers/net/ice/ice_dcf_ethdev.h
> > index 27f6402786..4baaec4b8b 100644
> > --- a/drivers/net/ice/ice_dcf_ethdev.h
> > +++ b/drivers/net/ice/ice_dcf_ethdev.h
> > @@ -64,12 +64,18 @@ struct ice_dcf_vf_repr {
> >  	struct ice_dcf_vlan outer_vlan_info; /* DCF always handle outer
> VLAN
> > */  };
> >
> > +enum ice_dcf_devrarg {
> > +	ICE_DCF_DEVARG_CAP,
> 
> Does ICE_DCF_DEVARG_CAP means no ACL?
> 
ICE_DCF_DEVARG_CAP means to check whether DCF enabled with
the ice_dcf_cap_check_handler.
Similarly, ICE_DCF_DEVARG_ACL means to check ACL status.

Thanks
Zhichao
> > +	ICE_DCF_DEVARG_ACL,
> > +};
> > +
> >  extern const struct rte_tm_ops ice_dcf_tm_ops;  void
> > ice_dcf_handle_pf_event_msg(struct ice_dcf_hw *dcf_hw,
> >  				 uint8_t *msg, uint16_t msglen);
> >  int ice_dcf_init_parent_adapter(struct rte_eth_dev *eth_dev);  void
> > ice_dcf_uninit_parent_adapter(struct rte_eth_dev *eth_dev);
> >
> > +int ice_devargs_check(struct rte_devargs *devargs, enum
> > +ice_dcf_devrarg devarg_type);
> >  int ice_dcf_vf_repr_init(struct rte_eth_dev *vf_rep_eth_dev, void
> > *init_param);  int ice_dcf_vf_repr_uninit(struct rte_eth_dev
> > *vf_rep_eth_dev);  int ice_dcf_vf_repr_init_vlan(struct rte_eth_dev
> > *vf_rep_eth_dev); diff --git a/drivers/net/ice/ice_dcf_parent.c
> > b/drivers/net/ice/ice_dcf_parent.c
> > index 2f96dedcce..c67c865d8e 100644
<snip for brevity>

      reply	other threads:[~2022-08-23  9:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25  3:15 [PATCH] " zhichaox.zeng
2022-08-12  4:08 ` Zhang, Qi Z
2022-08-17  8:21 ` [PATCH v2] " zhichaox.zeng
2022-08-22 23:07   ` Zhang, Qi Z
2022-08-23  7:33   ` Yang, Qiming
2022-08-23  9:16     ` Zeng, ZhichaoX [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=CO6PR11MB56028C70D9FBED671BD18631F1709@CO6PR11MB5602.namprd11.prod.outlook.com \
    --to=zhichaox.zeng@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@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).