From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9645DA04DB; Wed, 14 Oct 2020 23:36:25 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 78F231BF7D; Wed, 14 Oct 2020 23:36:24 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 709E71BEE0 for ; Wed, 14 Oct 2020 23:36:23 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 235BF5C0067; Wed, 14 Oct 2020 17:36:20 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 14 Oct 2020 17:36:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= XUCa1Ne4rUBm7BH5CJ/SXuz/YkWElC0sBo6Qq6/9ul0=; b=V0Dv7PnpAaDZ7xkq u+4QFAzwhlA4LfOvbBTm3wY23YxKVjlf2trgi97YLzWjK9k4AIbM/6hwbn9h5myv tRROG7GWA2rFuTdh40jZN//ceAJJWNs/YKi5cQiWrf2b2xdyhcz9bCzY0yFcxOJn R25pNBvDZvg3UH7yW61DqibhI5d9hqdm/6gHM8XndGbL+AUJIjl9794B9Rs1nQcJ LaRgzir9NUK+mr4+/3lQGz5Ehb/zNg6zxxvB9b9EgIPG4LnBCH4Yatne2AWF56/L y7frBbKGq18Mlu8p+XA70tXvYYnmFzt5fIKtP4RbD0eQuaPZ/z/WPkP6PSlbI4e1 PCEUmw== 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=XUCa1Ne4rUBm7BH5CJ/SXuz/YkWElC0sBo6Qq6/9u l0=; b=bkF8srB6ovy7U6I4QFEeYE8out8c9J4gAtC0LSoEX+CUi22gLKJqF5eqQ MUwKqZ8Wuc3AkL7ao54IlRDLxUkmI3jVFSLrRF1aR8HbMzU+Rpwt6y8sD1kjLM6/ 8exmqiL/6kZzfeon8N+E8X3GwbxZ6briIBqgPAXf3WWA4MH1OX7E1h4MCysIlK/S FSCSKWQfGWWakL39y1j386QKkkP/S3cqUIoePoum8Fb+Uqrfu9zs3Umelej4sZE8 +b6UGrCCRdCWY54JYuRGBjYoqheISMqnyP/tktI62bb2QqEjmkZ2g5bzVTqg+8w8 jRzmUz6KWkOPWDns325DGZ5wSg3/w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedriedvucetufdoteggodetrfdotffvucfrrh hofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgenuceurghi lhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurh ephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgrshcuofho nhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrth htvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeuieeivdff geehnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhn vght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id C93A33064682; Wed, 14 Oct 2020 17:36:18 -0400 (EDT) From: Thomas Monjalon To: Dmitry Kozlyuk Cc: dev@dpdk.org, Khoa To , Dmitry Malloy , Pallavi Kadam , Narcisa Ana Maria Vasile Date: Wed, 14 Oct 2020 23:36:17 +0200 Message-ID: <2470695.XMhHo4k61X@thomas> In-Reply-To: <20200925234123.GB2470@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> References: <20200911002207.31813-1-dmitry.kozliuk@gmail.com> <20200925233243.7302-3-dmitry.kozliuk@gmail.com> <20200925234123.GB2470@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 2/2] eal/windows: implement alarm API 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 26/09/2020 01:41, Narcisa Ana Maria Vasile: > On Sat, Sep 26, 2020 at 02:32:43AM +0300, Dmitry Kozlyuk wrote: > > Implementation is based on waitable timers Win32 API. When timer is set, > > a callback and its argument are supplied to the OS, while timer handle > > is stored in EAL alarm list. When timer expires, OS wakes up the > > interrupt thread and runs the callback. Upon completion it removes the > > alarm. > > > > Waitable timers must be set from the thread their callback will run in, > > eal_intr_thread_schedule() provides a way to schedule asyncronuous code > > execution in the interrupt thread. Alarm module builds synchronous timer > > setup on top of it. > > > > Windows alarms are not a type of DPDK interrupt handle and do not > > interact with interrupt module beyond executing in the same thread. > > > > Signed-off-by: Dmitry Kozlyuk > > Acked-by: Narcisa Vasile Applied, thanks