DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>
To: "Carrillo, Erik G" <erik.g.carrillo@intel.com>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	"Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v2 2/4] event/sw: report periodic event timer capability
Date: Thu, 11 Aug 2022 15:44:26 +0000	[thread overview]
Message-ID: <DM6PR11MB38682F95656A77E98D5AF16AA1649@DM6PR11MB3868.namprd11.prod.outlook.com> (raw)
In-Reply-To: <IA1PR11MB64184EE0BAB049229F227C54B9659@IA1PR11MB6418.namprd11.prod.outlook.com>

Hi Gabe,

> -----Original Message-----
> From: Carrillo, Erik G <erik.g.carrillo@intel.com>
> Sent: Thursday, August 11, 2022 2:22 AM
> To: Naga Harish K, S V <s.v.naga.harish.k@intel.com>; jerinj@marvell.com;
> Van Haaren, Harry <harry.van.haaren@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: [PATCH v2 2/4] event/sw: report periodic event timer capability
> 
> Hi Harish,
> 
> > -----Original Message-----
> > From: Naga Harish K, S V <s.v.naga.harish.k@intel.com>
> > Sent: Wednesday, August 10, 2022 2:10 AM
> > To: Carrillo, Erik G <erik.g.carrillo@intel.com>; jerinj@marvell.com;
> > Van Haaren, Harry <harry.van.haaren@intel.com>
> > Cc: dev@dpdk.org
> > Subject: [PATCH v2 2/4] event/sw: report periodic event timer
> > capability
> >
> > update the software eventdev pmd timer_adapter_caps_get callback
> > function to report the support of periodic event timer capability
> >
> > Signed-off-by: Naga Harish K S V <s.v.naga.harish.k@intel.com>
> > ---
> >  drivers/event/sw/sw_evdev.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/event/sw/sw_evdev.c b/drivers/event/sw/sw_evdev.c
> > index f93313b31b..89c07d30ae 100644
> > --- a/drivers/event/sw/sw_evdev.c
> > +++ b/drivers/event/sw/sw_evdev.c
> > @@ -564,7 +564,7 @@ sw_timer_adapter_caps_get(const struct
> > rte_eventdev *dev, uint64_t flags,  {
> >  	RTE_SET_USED(dev);
> >  	RTE_SET_USED(flags);
> > -	*caps = 0;
> > +	*caps = RTE_EVENT_TIMER_ADAPTER_CAP_PERIODIC;
> 
> It looks like we can add:
> 
> #define RTE_EVENT_TIMER_ADAPTER_SW_CAP \
> 	RTE_EVENT_TIMER_ADAPTER_CAP_PERIODIC
> 
> to eventdev_pmd.h (the same as RTE_EVENT_CRYPTO_ADAPTER_SW_CAP,
> for example),
> 
> and use that definition here, and in rte_event_timer_adapter_caps_get().
> 

Taken in v3 version of the patch

> Thanks,
> Erik
> 
> >
> >  	/* Use default SW ops */
> >  	*ops = NULL;
> > --
> > 2.25.1


  parent reply	other threads:[~2022-08-11 15:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 16:26 [PATCH " Naga Harish K S V
2022-08-05 12:00 ` Van Haaren, Harry
2022-08-10 11:01   ` Naga Harish K, S V
2022-08-10  7:09 ` [PATCH v2 " Naga Harish K S V
2022-08-10 20:52   ` Carrillo, Erik G
2022-08-11 15:33     ` Van Haaren, Harry
2022-08-11 15:44     ` Naga Harish K, S V [this message]
2022-08-11 15:37   ` [PATCH v3 " Naga Harish K S V
2022-08-12 16:07     ` [PATCH v4 " Naga Harish K S V
2022-09-06  8:10       ` Van Haaren, Harry
2022-09-09  5:33         ` Naga Harish K, S V
2022-08-10  7:01 [PATCH v2 " Naga Harish K S V

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=DM6PR11MB38682F95656A77E98D5AF16AA1649@DM6PR11MB3868.namprd11.prod.outlook.com \
    --to=s.v.naga.harish.k@intel.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=jerinj@marvell.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).