From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dharton@cisco.com> Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by dpdk.org (Postfix) with ESMTP id E9834567C for <users@dpdk.org>; Fri, 29 Apr 2016 01:50:59 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=616; q=dns/txt; s=iport; t=1461887459; x=1463097059; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=rWft4HRMhRWO8B+r3+bRTOpehWKhhTLYFCVYUdLSFJM=; b=FkffiQO7h5+u6HVArLi3CaZHqKGebcupfKptXOxbtY93XU/RyPHXNj7e 2ZDaIhRdz40YkSEw6/WhbNEsAEHryq4pMm9v9wfoUvHRHH3i3z33E7oyj VYS/1O8wL8Kx2fkl296erhaQW1jsqZ33QtMmCuIeQl32/gALGGChhG4F5 E=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DzAQB6oSJX/5BdJa1egziBVrliAQ2Bd?= =?us-ascii?q?oc3OBQBAQEBAQEBZRwLhEg6UQE+QiYBBBuIIqJBoQsBAQgCAR2GIY5eBZgQAY4?= =?us-ascii?q?PgViNQI8vAR4BAUKDa4dVfwEBAQ?= X-IronPort-AV: E=Sophos;i="5.24,549,1454976000"; d="scan'208";a="97172621" Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Apr 2016 23:50:31 +0000 Received: from XCH-ALN-018.cisco.com (xch-aln-018.cisco.com [173.36.7.28]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u3SNoVv3006712 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <users@dpdk.org>; Thu, 28 Apr 2016 23:50:31 GMT Received: from xch-rcd-016.cisco.com (173.37.102.26) by XCH-ALN-018.cisco.com (173.36.7.28) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 28 Apr 2016 18:50:31 -0500 Received: from xch-rcd-016.cisco.com ([173.37.102.26]) by XCH-RCD-016.cisco.com ([173.37.102.26]) with mapi id 15.00.1104.009; Thu, 28 Apr 2016 18:50:31 -0500 From: "David Harton (dharton)" <dharton@cisco.com> To: "users@dpdk.org" <users@dpdk.org> Thread-Topic: How To Handle Hot Remove? Thread-Index: AdGhp/MtDVjT/pEgRfCI2nk1376Hsg== Date: Thu, 28 Apr 2016 23:50:31 +0000 Message-ID: <c4831a0f3c574ca7bffd463b8a2301a7@XCH-RCD-016.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.82.253.116] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [dpdk-users] How To Handle Hot Remove? X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions <users.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/users>, <mailto:users-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/users/> List-Post: <mailto:users@dpdk.org> List-Help: <mailto:users-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/users>, <mailto:users-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 28 Apr 2016 23:51:00 -0000 I've looked at the docs online and in the git repo. I've also looked at wh= at is in test-pmd but I haven't found an answer to the following questions = around the scenario where a user pulls out the NIC card of an in-service sy= stem. Or another example would be a user removes an interface from the hos= t KVM config while the guest application is processing packets for that int= erface. 1) What notification does DPDK provide the application or to gracefully sto= p the device? 2) Is there any kind of ordering the application has to follow before calli= ng rte_eth_dev_detatch()? Thanks, Dave