From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH] eal: add asynchronous request API to DPDK IPC Date: Fri, 2 Mar 2018 10:51:32 -0800 Message-ID: <20180302105127.3e6f274f@xeon-e3> References: <92186ea34a31743ed76dbd9267f0586da22575f3.1519742486.git.anatoly.burakov@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, jianfeng.tan@intel.com, konstantin.ananyev@intel.com To: Anatoly Burakov Return-path: Received: from mail-pg0-f50.google.com (mail-pg0-f50.google.com [74.125.83.50]) by dpdk.org (Postfix) with ESMTP id C3D17325F for ; Fri, 2 Mar 2018 22:27:40 +0100 (CET) Received: by mail-pg0-f50.google.com with SMTP id l24so4278634pgc.5 for ; Fri, 02 Mar 2018 13:27:40 -0800 (PST) In-Reply-To: <92186ea34a31743ed76dbd9267f0586da22575f3.1519742486.git.anatoly.burakov@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, 27 Feb 2018 14:59:29 +0000 Anatoly Burakov wrote: > This API is similar to the blocking API that is already present, > but reply will be received in a separate callback by the caller. > > Under the hood, we create a separate thread to deal with replies to > asynchronous requests, that will just wait to be notified by the > main thread, or woken up on a timer (it'll wake itself up every > minute regardless of whether it was called, but if there are no > requests in the queue, nothing will be done and it'll go to sleep > for another minute). > > Signed-off-by: Anatoly Burakov The problem with this callback model is it makes it possible to have a single wait for multiple events model (like epoll) which is the most scaleable way to write applications.