From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, harry.van.haaren@intel.com, hemant.agrawal@nxp.com,
gage.eads@intel.com, nipun.gupta@nxp.com,
narender.vangati@intel.com
Subject: Re: [PATCH] eventdev: clarify the worker thread workflow
Date: Thu, 1 Jun 2017 10:06:55 +0530 [thread overview]
Message-ID: <20170601043653.GA18613@jerin> (raw)
In-Reply-To: <20170518112059.GA2020@bricha3-MOBL3.ger.corp.intel.com>
-----Original Message-----
> Date: Thu, 18 May 2017 12:20:59 +0100
> From: Bruce Richardson <bruce.richardson@intel.com>
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> CC: dev@dpdk.org, harry.van.haaren@intel.com, hemant.agrawal@nxp.com,
> gage.eads@intel.com, nipun.gupta@nxp.com, narender.vangati@intel.com
> Subject: Re: [dpdk-dev] [PATCH] eventdev: clarify the worker thread workflow
> User-Agent: Mutt/1.8.0 (2017-02-23)
>
> On Thu, May 18, 2017 at 04:40:41PM +0530, Jerin Jacob wrote:
> > If the RTE_EVENT_DEV_CAP_DISTRIBUTED_SCHED capability flag
> > is not set indicates the device is centralized and thus needs
> > a dedicated scheduling thread that repeatedly calls
> > rte_event_schedule().
> >
> > Update the worker thread code snippet to match
> > the description.
> >
> > Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> > ---
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied to dpdk-next-eventdev/master. Thanks.
>
prev parent reply other threads:[~2017-06-01 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 11:10 [PATCH] eventdev: clarify the worker thread workflow Jerin Jacob
2017-05-18 11:20 ` Bruce Richardson
2017-06-01 4:36 ` Jerin Jacob [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=20170601043653.GA18613@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=narender.vangati@intel.com \
--cc=nipun.gupta@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.