From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 35D7233E; Fri, 13 Jul 2018 06:44:19 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 13 Jul 2018 06:44:19 -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=o721zKXmg7aKAqlToCvhTljzEa XZVK/Ajpru08nkV9c=; b=pS+PlAzioAzaOc//qQovhPLyGEoiB5MDSIxB0XSlz/ a8Z++2QYCFh63XXHwWzxN04Diz4kRdLgZueiIfQyEzG/0kPaNfGoyH+jwFFrRSSn 8muE5L+xKmQpMC13LOA855h1yG0oWkXPGyzc7Qxir6I8DN72/62up3mOEu1Wweq5 4= 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=fm3; bh=o721zK Xmg7aKAqlToCvhTljzEaXZVK/Ajpru08nkV9c=; b=O4mR4MxeWf1b/EzR3G+opl DOi9KPwf8uCiym2ZHTg4UoKRlKwVOZfQEnrmB6Y7iXycJguM8ezKtNd4gM22LIjs YquIghenF4afnQkxLcgtqQmzwLc7QSZyG8aYN2brHR2SBzin+IxH+lz/vw8qrtZ0 kFNmj9pmCCPvllQvFcuDEzZuK9Mb9NL7Mx5rrjkkST+qHzf1j9CpUSnhD/mCf1ib 10dpxqZCWtsorcg9beEGg1IymOvxQpfXEJCEDedTgosJ5GY6TOR0g4Pj6RAvSgNY ce6nRrChfJkDSxNZ7jhTEmo7ZLIg/doTB07TSDQU8FAqUSx01hvAEs5mBUdR2Jrg == X-ME-Proxy: 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 C4A35E49E9; Fri, 13 Jul 2018 06:44:17 -0400 (EDT) From: Thomas Monjalon To: Anatoly Burakov Cc: dev@dpdk.org, konstantin.ananyev@intel.com, bruce.richardson@intel.com, qi.z.zhang@intel.com Date: Fri, 13 Jul 2018 12:44:16 +0200 Message-ID: <2912332.Lmy7lc5DGs@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 0/7] Remove asynchronous IPC thread 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: Fri, 13 Jul 2018 10:44:20 -0000 > 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 :)