From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 3CA1D56A1 for ; Thu, 19 Apr 2018 17:22:26 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id C95D221B31; Thu, 19 Apr 2018 11:22:25 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 19 Apr 2018 11:22:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=iHrpRJRFaR70NBCGoOPxgK/IhA kgFUDG++cwMXaON0Y=; b=fNeifv957qOE1W5/YW+JdPxtIiRC+dXytDwH0SJuYD WtzEhYwEndAUco27n3j/k44JsFVyS2xcNcMWQsJ2pLKSnXmv6p1q8ezJy9lGwFZl zuTUwyAm4owrIv9uHQg9ph0JMlRUXMgwRgh1slmqAtXdQ5CqR68ph9rAs0gcVRpW U= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=iHrpRJ RFaR70NBCGoOPxgK/IhAkgFUDG++cwMXaON0Y=; b=Qy5RSOJTndh5JAScnYSVUI eAAH49EH6030Mc0S0DI56barsVZUvY5cmfMr0K9RkH424psSOsiO88SBjIVxJlqw vj5M+9UH1LTzyxw//GPea4kCX8Dc786O2czkEWNSRDhwfxlNyN076F/6HRcZBKOJ ZViT1ravFm8fyPgRKmaGruLK7ln+9MLkgSZXBoodvFk5B+sjjAisSrbIvpi85xTd isSz8MXKDrEDQVAwESj6EqMXUJXGVGiRjKK8wz/VkYi850kerdy3VzGZMlnuuIEE YcL9M93+UO+v3iJjGFgcoHd/1tmCNqGhmZj6kTPStVFzeYZZyyniScNaFhTo3QiA == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 1C2D0E443C; Thu, 19 Apr 2018 11:22:25 -0400 (EDT) From: Thomas Monjalon To: Jianfeng Tan Cc: dev@dpdk.org, anatoly.burakov@intel.com Date: Thu, 19 Apr 2018 17:22:23 +0200 Message-ID: <2792230.YcD1pZkY78@xps> In-Reply-To: <1524150216-3407-1-git-send-email-jianfeng.tan@intel.com> References: <1524150216-3407-1-git-send-email-jianfeng.tan@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [RFC 0/8] remove IPC threads X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2018 15:22:26 -0000 19/04/2018 17:03, Jianfeng Tan: > As discussed here, http://dpdk.org/dev/patchwork/patch/36579/, we will > try best to avoid thread creation in the library. Now we have two threads > for IPC, rte_mp_handle and rte_mp_handle_async. This patchset is to > finish the job. Thanks for working on it. > This patchset: > - is rebased on commit 34345a9b69bb ("eventdev: fix build with icc"). > - also needs http://dpdk.org/dev/patchwork/patch/37335/ > > Patch 1~2: code cleanup and bug fix. (Target for v18.05) > Patch 3~4: Remove IPC async thread. (Target for v18.08) > Patch 5~8: Remove IPC thread. (Target for v18.08) You should send fixes for 18.05 in a separate series. It is preferred to merge full series or nothing.