From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <bruce.richardson@intel.com> Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 46D7020F for <dev@dpdk.org>; Thu, 18 May 2017 13:21:04 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 May 2017 04:21:03 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,358,1491289200"; d="scan'208";a="970128378" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.42]) by orsmga003.jf.intel.com with SMTP; 18 May 2017 04:21:00 -0700 Received: by (sSMTP sendmail emulation); Thu, 18 May 2017 12:20:59 +0100 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 Message-ID: <20170518112059.GA2020@bricha3-MOBL3.ger.corp.intel.com> References: <20170518111041.843-1-jerin.jacob@caviumnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170518111041.843-1-jerin.jacob@caviumnetworks.com> Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.8.0 (2017-02-23) Subject: Re: [dpdk-dev] [PATCH] eventdev: clarify the worker thread workflow X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 18 May 2017 11:21:05 -0000 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>