From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail04.ics.ntt-tx.co.jp (mail05.ics.ntt-tx.co.jp [210.232.35.69]) by dpdk.org (Postfix) with ESMTP id D06165699 for ; Mon, 10 Dec 2018 08:54:17 +0100 (CET) Received: from gwchk03.silk.ntt-tx.co.jp (gwchk03.silk.ntt-tx.co.jp [10.107.0.111]) by mail04.ics.ntt-tx.co.jp (unknown) with ESMTP id wBA7sFM8025347 for unknown; Mon, 10 Dec 2018 16:54:15 +0900 Received: (from root@localhost) by gwchk03.silk.ntt-tx.co.jp (unknown) id wBA7sFx2003402 for unknown; Mon, 10 Dec 2018 16:54:15 +0900 Received: from gwchk.silk.ntt-tx.co.jp [10.107.0.110] by gwchk03.silk.ntt-tx.co.jp with ESMTP id SAA03401; Mon, 10 Dec 2018 16:54:15 +0900 Received: from imss06.silk.ntt-tx.co.jp (localhost [127.0.0.1]) by ccmail04.silk.ntt-tx.co.jp (unknown) with ESMTP id wBA7sF9j022339 for unknown; Mon, 10 Dec 2018 16:54:15 +0900 Received: from imss06.silk.ntt-tx.co.jp (localhost [127.0.0.1]) by imss06.silk.ntt-tx.co.jp (unknown) with ESMTP id wBA7sF9V025314 for unknown; Mon, 10 Dec 2018 16:54:15 +0900 Received: from ccmail04 (smtp03.silk.ntt-tx.co.jp [10.107.0.135]) by imss06.silk.ntt-tx.co.jp (unknown) with SMTP id wBA7sFXZ025311 for unknown; Mon, 10 Dec 2018 16:54:15 +0900 Date: Mon, 10 Dec 2018 16:53:01 +0900 From: Hideyuki Yamashita In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-2022-JP" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.74 [ja] X-CCMail7: CC-Mail-V7.0.2-Client-Relayed Message-Id: <201812100754.wBA7s5ZE022173@ccmail04.silk.ntt-tx.co.jp> X-TM-AS-MML: No X-CC-Mail-RelayStamp: CC-Mail-V5.14-Server To: dev@dpdk.org Subject: [dpdk-dev] rte_eal_hotplug_remove() generates error message 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: Mon, 10 Dec 2018 07:54:18 -0000 Subject: Dear Thomas and all, I hope you all get safely back home after DPDK summit. (When I get back Japan, it is chilling. (start of winter)) On DPDK 18.11.0, we tried to remove vhost device by using rte_eal_hotplug_remove(). However, following syslog message is printed. “EAL: Error: Invalid memory” At DPDK summit San Jose, we had chance to ask Thomas how to handle the error message, and he gave us following advice: Replace “rte_eal_hotplug_add()” to “rte_dev_probe(devargs)” and “rte_eal_hotplug_remove()” to “rte_eth_dev_close() and rte_dev_remove(rte_dev)” We tested above changes, but the result is the same (i.e., same error message is printed). The debug log message says: --- [primary] VHOST_CONFIG: vhost-user server: socket created, fd: 17 VHOST_CONFIG: bind to /tmp/sock0 EAL: Error: Invalid memory VHOST_CONFIG: vhost-user server: socket created, fd: 17 VHOST_CONFIG: bind to /tmp/sock0 [secondary] APP: devargs=eth_vhost0,iface=/tmp/sock0,queues=1 EAL: request: eal_dev_mp_request EAL: msg: eal_dev_mp_request EAL: request: bus_vdev_mp EAL: msg: bus_vdev_mp EAL: msg: bus_vdev_mp EAL: reply: eal_dev_mp_request EAL: msg: eal_dev_mp_request rte_eth_promiscuous_disable: Function not supported rte_eth_allmulticast_disable: Function not supported APP: To Server: add EAL: request: eal_dev_mp_request EAL: msg: eal_dev_mp_request EAL: reply: eal_dev_mp_request EAL: msg: eal_dev_mp_request APP: To Server: del APP: devargs=eth_vhost0,iface=/tmp/sock0,queues=1 EAL: request: eal_dev_mp_request EAL: msg: eal_dev_mp_request EAL: request: bus_vdev_mp EAL: msg: bus_vdev_mp EAL: msg: bus_vdev_mp EAL: reply: eal_dev_mp_request EAL: msg: eal_dev_mp_request rte_eth_promiscuous_disable: Function not supported rte_eth_allmulticast_disable: Function not supported APP: To Server: add --- We would like to ask: 1) Is the message “EAL: Error: Invalid memory” ignorable or not? There is no obstacle except this message to re-add the vhost device. 2) Which is the better(best?) way to add/del vhost device “rte_eal_hotplug_add/remove()” or the way Thomas suggested? Thanks in advance and have a nice day. BR, Hideyuki Yamashita NTT TechnoCross