From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <keith.wiles@intel.com>
Received: from mga05.intel.com (mga05.intel.com [192.55.52.43])
 by dpdk.org (Postfix) with ESMTP id 0CD932986
 for <dev@dpdk.org>; Wed, 17 May 2017 16:51:36 +0200 (CEST)
Received: from orsmga005.jf.intel.com ([10.7.209.41])
 by fmsmga105.fm.intel.com with ESMTP; 17 May 2017 07:51:36 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.38,354,1491289200"; d="scan'208";a="101746337"
Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205])
 by orsmga005.jf.intel.com with ESMTP; 17 May 2017 07:51:36 -0700
Received: from fmsmsx120.amr.corp.intel.com (10.18.124.208) by
 fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS)
 id 14.3.319.2; Wed, 17 May 2017 07:51:35 -0700
Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.235]) by
 fmsmsx120.amr.corp.intel.com ([169.254.15.77]) with mapi id 14.03.0319.002;
 Wed, 17 May 2017 07:51:35 -0700
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
CC: DPDK <dev@dpdk.org>
Thread-Topic: Discuss plugin threading model for DPDK.
Thread-Index: AQHSzx0U+bVW6+alkEG3WQlmwWpOsA==
Date: Wed, 17 May 2017 14:51:34 +0000
Message-ID: <15608565-A4D5-48C0-BD0D-4A4D399BE3D9@intel.com>
References: <1493810961-139469-1-git-send-email-harry.van.haaren@intel.com>
 <5129240.aMJQgb24zL@xps>
 <20170517103228.GA14292@bricha3-MOBL3.ger.corp.intel.com>
 <3696663.2JsLXSjzmN@xps>
In-Reply-To: <3696663.2JsLXSjzmN@xps>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.34.72.41]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <906A9B91FD5E9341BA4D1ACC9BD8365A@intel.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dpdk-dev] Discuss plugin threading model for DPDK.
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: Wed, 17 May 2017 14:51:37 -0000


> On May 17, 2017, at 4:28 AM, Thomas Monjalon <thomas@monjalon.net> wrote:
>=20
> OK to register CPU needs for services (including interrupts processing).
>=20
> Then we could take this opportunity to review how threads are managed.
> We will have three types of cores:
> - not used
> - reserved for services
> - used for polling / application processing
> It is fine to reserve/define CPU from DPDK point of view.
>=20
> Then DPDK launch threads on cores. Maybe we should allow the application
> to choose how threads are launched and managed.
> Keith was talking about a plugin approach for thread management I think.
Thomas,
So, not to hijack this thread or maybe I misunderstood your comment I chang=
ed the subject.

Maybe we can look at the plugin model for a DPDK threading model to allow s=
omeone to use their own threading solution.

Is this required or just another enhancement?

Regards,
Keith