From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2 0/7] Remove asynchronous IPC thread Date: Fri, 13 Jul 2018 12:44:16 +0200 Message-ID: <2912332.Lmy7lc5DGs@xps> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, konstantin.ananyev@intel.com, bruce.richardson@intel.com, qi.z.zhang@intel.com To: Anatoly Burakov Return-path: Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by dpdk.org (Postfix) with ESMTP id 989E04F94 for ; Fri, 13 Jul 2018 12:44:20 +0200 (CEST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > Anatoly Burakov (4): > eal/bsdapp: add interrupt thread > eal/bsdapp: add alarm support > ipc: remove IPC thread for async requests > doc: document IPC callback limitations > > Jianfeng Tan (3): > eal/linux: use glibc malloc in alarm > eal/linux: use glibc malloc in interrupt handling > eal: bring forward init of interrupt handling Applied, thanks Crossing fingers that moving interrupt init will have no consequence :)