From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Carrillo, Erik G" <erik.g.carrillo@intel.com>,
dev@dpdk.org, "Richardson, Bruce" <bruce.richardson@intel.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"Eads, Gage" <gage.eads@intel.com>,
"nipun.gupta@nxp.com" <nipun.gupta@nxp.com>,
"Vangati, Narender" <narender.vangati@intel.com>,
"Rao, Nikhil" <nikhil.rao@intel.com>,
"pbhagavatula@caviumnetworks.com"
<pbhagavatula@caviumnetworks.com>,
"jianbo.liu@linaro.org" <jianbo.liu@linaro.org>,
"rsanford@akamai.com" <rsanford@akamai.com>
Subject: Re: [dpdk-dev] [RFC PATCH 0/1] eventtimer: introduce event timer wheel
Date: Tue, 29 Aug 2017 21:37:06 +0530 [thread overview]
Message-ID: <20170829160705.GA14529@jerin> (raw)
In-Reply-To: <17506826.eAYivCQaQA@xps>
-----Original Message-----
> Date: Tue, 29 Aug 2017 17:48:58 +0200
> From: Thomas Monjalon <thomas@monjalon.net>
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Cc: "Carrillo, Erik G" <erik.g.carrillo@intel.com>, dev@dpdk.org,
> "Richardson, Bruce" <bruce.richardson@intel.com>, "Van Haaren, Harry"
> <harry.van.haaren@intel.com>, "hemant.agrawal@nxp.com"
> <hemant.agrawal@nxp.com>, "Eads, Gage" <gage.eads@intel.com>,
> "nipun.gupta@nxp.com" <nipun.gupta@nxp.com>, "Vangati, Narender"
> <narender.vangati@intel.com>, "Rao, Nikhil" <nikhil.rao@intel.com>,
> "pbhagavatula@caviumnetworks.com" <pbhagavatula@caviumnetworks.com>,
> "jianbo.liu@linaro.org" <jianbo.liu@linaro.org>, "rsanford@akamai.com"
> <rsanford@akamai.com>
> Subject: Re: [dpdk-dev] [RFC PATCH 0/1] eventtimer: introduce event timer
> wheel
>
> 29/08/2017 17:41, Jerin Jacob:
> > From: Thomas Monjalon <thomas@monjalon.net>
> > > 25/08/2017 12:25, Jerin Jacob:
> > > > From: "Carrillo, Erik G" <erik.g.carrillo@intel.com>
> > > [...]
> > > > > In summary, it looks like our solutions align fairly well, and I propose that we take on the software implementation if there are no objections.
> > > >
> > > > Sure, no objection.
> > >
> > > Good to see such a basic function generalized for NPU and CPU.
> > >
> > > Are you going to use rte_timer for CPU implementation?
> > > Does it mean that event_timer supersedes rte_timer?
> >
> > IMO, we don't need to supersedes the rte_timer. The eventdev or event_timer is
> > an optional component. It is application decision to use poll mode vs event
> > driver model or combination of two.
>
> Trying to make clear when using poll mode or event model,
> regarding CPU/NPU differences:
> If using poll mode + rte_timer, we cannot leverage NPU offloads.
Yes.
> If using event model, is it as much efficient for generic CPU?
It is case by case. I think, ATOMIC queues and PARALLEL queues can be
effectively implemented for the generic CPU. ORDERED queue(the reordering
business) may not very effective. So it is boiled down to application
requirements.
next prev parent reply other threads:[~2017-08-29 16:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 16:11 Jerin Jacob
2017-08-17 16:11 ` [dpdk-dev] [RFC PATCH 1/1] " Jerin Jacob
2017-08-23 22:57 ` [dpdk-dev] [RFC PATCH 0/1] " Carrillo, Erik G
2017-08-25 10:25 ` Jerin Jacob
2017-08-29 15:02 ` Thomas Monjalon
2017-08-29 15:41 ` Jerin Jacob
2017-08-29 15:48 ` Thomas Monjalon
2017-08-29 16:07 ` Jerin Jacob [this message]
2017-09-22 15:17 ` [dpdk-dev] [RFC PATCH v2 0/1] eventtimer: introduce event timer adapter Erik Gabriel Carrillo
2017-09-22 15:17 ` [dpdk-dev] [RFC PATCH v2 1/1] " Erik Gabriel Carrillo
2017-10-03 14:37 ` [dpdk-dev] [RFC PATCH v2 0/1] " Jerin Jacob
2017-10-09 20:30 ` Carrillo, Erik G
2017-10-16 12:04 ` Pavan Nikhilesh Bhagavatula
2017-10-16 12:37 ` Pavan Nikhilesh Bhagavatula
2017-10-18 21:48 ` Carrillo, Erik G
2017-10-26 15:45 ` Pavan Nikhilesh Bhagavatula
2017-11-20 22:35 ` [dpdk-dev] [RFC PATCH v3 " Erik Gabriel Carrillo
2017-11-20 22:35 ` [dpdk-dev] [RFC PATCH v3 1/1] " Erik Gabriel Carrillo
2017-11-23 4:37 ` Pavan Nikhilesh Bhagavatula
2017-11-27 14:47 ` Carrillo, Erik G
2017-11-28 17:40 ` [dpdk-dev] [RFC PATCH v4 0/4] " Erik Gabriel Carrillo
2017-11-28 17:40 ` [dpdk-dev] [RFC PATCH v4 1/4] " Erik Gabriel Carrillo
2017-11-29 10:29 ` Pavan Nikhilesh Bhagavatula
2017-11-28 17:40 ` [dpdk-dev] [RFC PATCH v4 2/4] eventtimer: add common code Erik Gabriel Carrillo
2017-11-29 5:19 ` Pavan Nikhilesh Bhagavatula
2017-11-30 20:59 ` Carrillo, Erik G
2017-12-01 5:13 ` Pavan Nikhilesh Bhagavatula
2017-12-01 20:19 ` Carrillo, Erik G
2017-11-28 17:40 ` [dpdk-dev] [RFC PATCH v4 3/4] eventtimer: add default software implementation stub Erik Gabriel Carrillo
2017-11-29 10:34 ` Pavan Nikhilesh Bhagavatula
2017-11-30 23:56 ` Carrillo, Erik G
2017-12-01 5:15 ` Pavan Nikhilesh Bhagavatula
2017-11-28 17:40 ` [dpdk-dev] [RFC PATCH v4 4/4] test: add event timer adapter auto-test Erik Gabriel Carrillo
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=20170829160705.GA14529@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=gage.eads@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jianbo.liu@linaro.org \
--cc=narender.vangati@intel.com \
--cc=nikhil.rao@intel.com \
--cc=nipun.gupta@nxp.com \
--cc=pbhagavatula@caviumnetworks.com \
--cc=rsanford@akamai.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).