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 3B00B1B161 for ; Sun, 7 Jan 2018 10:54:06 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6234A20985; Sun, 7 Jan 2018 04:54:04 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 07 Jan 2018 04:54:04 -0500 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=rucpwQQpU7Yn5GOYdIBayyYrxT JBIUdBeyUGZRqmXkk=; b=TYZ+11F4GW+6YKVAv9E9KrbMNp6XCmU6rsF9HFIeVK KdlIc+fv2W64gmdVnmIXCFqT2uE364SIY5eIQrq7RpAlDn6xiXYYjyHskcDhYJiI xAt7P7StjPDAgssjLSwq/0XfYOVJm3eCwDEMFC4/0l9BWx+uipfLe0/t/rS0I/SB 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=fm1; bh=rucpwQ QpU7Yn5GOYdIBayyYrxTJBIUdBeyUGZRqmXkk=; b=AdO9lHWhf0qxERXLNhlrvx hU6EB9hh5mBYbuE+CaRFUp2q1zHvRXO9qcZOT6lvJJyVPkI3yY7m5glTFHl1R0ze Nl/IMbPKyQW8AoWSORSXE9WL1rFzXSjEwbCG6GdK/i+PLxf5Sg6c/aZvONUofa5F uN8z1i8cviAc6vq71gMtj4rD/thjpAilhvt2Hztp87Z3lhPb8YgoQXngybEuwbIU gslelrJ4Kh7ukZBy5uNlTiSZlpeYcr+AFkMgLNHLpPgB83mj5YkGYPENMubKPQHq ktcXJre7VuSBk+2q1tksxEaP9dmpQXvqgf/lB5lYDJzOb/HlZ/VRKPg6XPDz8VmQ == 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 15E537E3DF; Sun, 7 Jan 2018 04:54:04 -0500 (EST) From: Thomas Monjalon To: Matan Azrad Cc: dev@dpdk.org, Adrien Mazarguil , Gaetan Rivet Date: Sun, 07 Jan 2018 10:53:40 +0100 Message-ID: <1580512.5EzYo8qsNT@xps> In-Reply-To: <1513703415-29145-2-git-send-email-matan@mellanox.com> References: <1513175370-16583-1-git-send-email-matan@mellanox.com> <1513703415-29145-1-git-send-email-matan@mellanox.com> <1513703415-29145-2-git-send-email-matan@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 1/6] ethdev: add devop to check removal status 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: Sun, 07 Jan 2018 09:54:06 -0000 19/12/2017 18:10, Matan Azrad: > There is time between the physical removal of the device until PMDs get > a RMV interrupt. At this time DPDK PMDs and applications still don't > know about the removal. > > Current removal detection is achieved only by registration to device RMV > event and the notification comes asynchronously. So, there is no option > to detect a device removal synchronously. > Applications and other DPDK entities may want to check a device removal > synchronously and to take an immediate decision accordingly. > > Add new dev op called is_removed to allow DPDK entities to check an > Ethernet device removal status immediately. > > Signed-off-by: Matan Azrad Acked-by: Thomas Monjalon