From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout3.w1.samsung.com (mailout3.w1.samsung.com [210.118.77.13]) by dpdk.org (Postfix) with ESMTP id E7DEB298F for ; Wed, 24 Feb 2016 16:05:00 +0100 (CET) Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245]) by mailout3.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0O3200NZ84KA0G30@mailout3.w1.samsung.com> for dev@dpdk.org; Wed, 24 Feb 2016 15:04:58 +0000 (GMT) X-AuditID: cbfec7f5-f79b16d000005389-57-56cdc69a4232 Received: from eusync2.samsung.com ( [203.254.199.212]) by eucpsbgm2.samsung.com (EUCPMTA) with SMTP id C5.6B.21385.A96CDC65; Wed, 24 Feb 2016 15:04:58 +0000 (GMT) Received: from fedinw7x64 ([106.109.131.169]) by eusync2.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTPA id <0O32007O24K9RU60@eusync2.samsung.com>; Wed, 24 Feb 2016 15:04:58 +0000 (GMT) From: Pavel Fedin To: "'Pattan, Reshma'" References: <1455289045-25915-1-git-send-email-reshma.pattan@intel.com> <014201d16a55$d05e4b20$711ae160$@samsung.com> <3AEA2BF9852C6F48A459DA490692831FFC6353@IRSMSX109.ger.corp.intel.com> In-reply-to: <3AEA2BF9852C6F48A459DA490692831FFC6353@IRSMSX109.ger.corp.intel.com> Date: Wed, 24 Feb 2016 18:04:57 +0300 Message-id: <030301d16f14$ba106240$2e3126c0$@samsung.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-index: AQIv6L0UmHAJ53r3gd8NJkyOKRJNhwF/yCYuAhOGCLieYbyw4A== Content-language: ru X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFLMWRmVeSWpSXmKPExsVy+t/xK7qzjp0NM+h+KWTx7tN2JovlX2aw ODB5/FqwlNVj8Z6XTAFMUVw2Kak5mWWpRfp2CVwZWydsYyr4zFHx5dJPxgbGz2xdjJwcEgIm Et+3/GWHsMUkLtxbDxTn4hASWMoo8eHzSkYI5zujxJkn6xlBqtgE1CVOf/3AAmKLCBhIfGg8 AmYzCwhIPL73jBWiYT+jxO8ns5hAEpwCIRLLD+wBWyEMZC+aPwcsziKgKnH27wNWEJtXwFJi 9rWfULagxI/J96CGakms33mcCcKWl9i85i0zxKkKEjvOvmaEOMJJYvar51D1IhLT/t1jnsAo NAvJqFlIRs1CMmoWkpYFjCyrGEVTS5MLipPSc430ihNzi0vz0vWS83M3MUJC/OsOxqXHrA4x CnAwKvHwPthwJkyINbGsuDL3EKMEB7OSCG/pgbNhQrwpiZVVqUX58UWlOanFhxilOViUxHln 7nofIiSQnliSmp2aWpBaBJNl4uCUamCUF2wPdgvn+bUjtGv3wWmVc7NmS9TGyp1u61cqX/Hi lIz99T3Wsc2NbL8NOaY1TOZ5tsfkwN6mD+ZbOUwXlx+wZDM7sbLa7+yLOUxmG6zjN2ZfOfE0 tOiWgfXi95IOqw72HnPa++twzguTzE2r9bv3OG//p1v67dVdef2XbsaPkzau3Roo/mytEktx RqKhFnNRcSIAaa5YB20CAAA= Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v2 0/5] add dpdk packet capture support for tcpdump X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Feb 2016 15:05:01 -0000 Hello! > > 2. What if i don't want separate RX and TX streams either? It only prevents me > > from seeing the complete picture. > > Do you mean not to have separate pcap files for tx and rx? If so, I would prefer to keep this > as it is. I mean - add an option not to have separate files. > Because pcap changes need to be replaced with TUN/TAP pmd once available in future. I believe it's lo-o-o-ong way to get there... > > 3. vhostuser ports are missing. Perhaps not really related to this patchset, i just > > don't know how much code "server" part of vhostuser shares with normal PMDs, > > but anyway, ability to dump them too would be nice to have. > > > > I think this can be done in future i.e. when vhost as PMD is available. But as of now vhost > is library. I expected "server"-side vhost to be the same as "client" part (AKA virtio), just use another mechanism for exchanging control information (via socket). Is it not true? I suppose, driving queues from both sides should be quite symmetric. Kind regards, Pavel Fedin Senior Engineer Samsung Electronics Research center Russia