From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f44.google.com (mail-pg0-f44.google.com [74.125.83.44]) by dpdk.org (Postfix) with ESMTP id C45AC7D56 for ; Wed, 23 Aug 2017 18:54:04 +0200 (CEST) Received: by mail-pg0-f44.google.com with SMTP id u191so2399381pgc.2 for ; Wed, 23 Aug 2017 09:54:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=imz+6AJg6qhl2BsGKJZLnSdPZKFbHh1Eck16zjtMLf4=; b=EaC1nUxVhmDy+ZWq6H8Ag2ScPCM/xjgPF/m9rQ95NPm4rHoe6psmVyY+jXHgeu8PKU wR8bquBk4UK4pqbgFznBOes8WFMbvBMDLC9nU1ElKV6PEO5D/guy5B+ODxEjZXtkkphP tmY+WwB/nB2FG/Co8+Z5Yjve1Syj+H+2VUwQEpblkHTzrQT+WNUwhdCjLxy59vQESqNS bAcLPx6lPFBJ90jLzKvkHccCpvDU8b70Nd1JyXyp0oikbQ/PvezwlXl3uDgGFnJfnNMM gTSh8KZL3qWr7ZRGJe3oPclRszZn6V2eQq13UXu8rWL02Y5r4rhWjkSl8F4phBWH0aJe UgRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=imz+6AJg6qhl2BsGKJZLnSdPZKFbHh1Eck16zjtMLf4=; b=Mjp5+HtHLUWcihWE+qfxWftZu/1JxlKdQeEOUc4WQVbMmXaGLYGGhMSAKzJYyvOOeT TSLeQT9DoIPoI7XP5H+G9trx3BmiBDQSckLXToDDhIgydFh47Asc7EvsluFmShQvLza4 465x4TQxlj364nI/Tso8dmyryBA73ZQjHpoTlmtpd5P2FLXeC//0dB+6HcPqmwsDb8Tk KSQUReS9tB55rpugohwLF/ZxaIl3sQSghPzyRrNhdtC+Uk4R9iJDlTVdTcC3/Six/MOG EcsN+E4iCruQktH6eYv1QLwE7W6mj7/GscUwLgrS8O5uVpOvE7EO+VwudPpP/ycmJvh8 6J9w== X-Gm-Message-State: AHYfb5hlohn0S4GqxVEau9eQnj/U7PFNdfykrnBBrusHdFy7wqb6L3va OthZc03O14WOW4yNDGlVLg== X-Received: by 10.84.149.139 with SMTP id m11mr347553pla.7.1503507244001; Wed, 23 Aug 2017 09:54:04 -0700 (PDT) Received: from xeon-e3 (76-14-207-240.or.wavecable.com. [76.14.207.240]) by smtp.gmail.com with ESMTPSA id w66sm3935969pfi.63.2017.08.23.09.54.03 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 23 Aug 2017 09:54:03 -0700 (PDT) Date: Wed, 23 Aug 2017 09:53:57 -0700 From: Stephen Hemminger To: Stuart Xu Cc: "users@dpdk.org" Message-ID: <20170823095357.581a6ccc@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-users] How to identify a network port which is bound to DPDK X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Aug 2017 16:54:05 -0000 On Tue, 22 Aug 2017 23:25:35 +0000 Stuart Xu wrote: > Hi, I understand that the DPDK uses port_id to identify an Ethernet port.= Is there a shell command to show a port=E2=80=99s status, such as link st= atus and port ID etc. For non-DPDK bound port I can use tools like =E2=80= =9Cifconfig=E2=80=9D. Does DPDK provide an =E2=80=9Cifconfig=E2=80=9D equi= valent tool to check a port status? >=20 DPDK network interfaces are not visible or controlled by kernel. There are some ways to expose them i.e through KNI and some other proposed = code.