From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id EA49B5AB3 for ; Mon, 29 Feb 2016 17:11:50 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 29 Feb 2016 08:11:46 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,521,1449561600"; d="scan'208";a="923515767" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by orsmga002.jf.intel.com with ESMTP; 29 Feb 2016 08:11:44 -0800 Received: from irsmsx111.ger.corp.intel.com (10.108.20.4) by IRSMSX104.ger.corp.intel.com (163.33.3.159) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 29 Feb 2016 16:11:43 +0000 Received: from irsmsx109.ger.corp.intel.com ([169.254.13.100]) by irsmsx111.ger.corp.intel.com ([169.254.2.198]) with mapi id 14.03.0248.002; Mon, 29 Feb 2016 16:11:43 +0000 From: "Pattan, Reshma" To: Pavel Fedin Thread-Topic: [dpdk-dev] [PATCH v2 0/5] add dpdk packet capture support for tcpdump Thread-Index: AQHRZaW781Y67aEH/E2nk2UFTSFmQ58x4FMAgAfJAmCAAbTSgIAH6fDw Date: Mon, 29 Feb 2016 16:11:42 +0000 Message-ID: <3AEA2BF9852C6F48A459DA490692831FFC77DD@IRSMSX109.ger.corp.intel.com> References: <1455289045-25915-1-git-send-email-reshma.pattan@intel.com> <014201d16a55$d05e4b20$711ae160$@samsung.com> <3AEA2BF9852C6F48A459DA490692831FFC6353@IRSMSX109.ger.corp.intel.com> <030301d16f14$ba106240$2e3126c0$@samsung.com> In-Reply-To: <030301d16f14$ba106240$2e3126c0$@samsung.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZTMyYTY5NjctZDk4MS00OThhLThiMWMtYjE3NzBlOWQ2NjAyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6Imc0RzVYd1B6TldIVGl6WGdhbnNPN2czK2UwdHBIaWFNRG1qbG9yelNodVE9In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: Mon, 29 Feb 2016 16:11:51 -0000 Hi, > -----Original Message----- > From: Pavel Fedin [mailto:p.fedin@samsung.com] > Sent: Wednesday, February 24, 2016 3:05 PM > To: Pattan, Reshma > Cc: dev@dpdk.org > Subject: RE: [dpdk-dev] [PATCH v2 0/5] add dpdk packet capture support fo= r > tcpdump >=20 > Hello! >=20 > > > 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. >=20 > I mean - add an option not to have separate files. OK, I will make changes in v3. >=20 > > > 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 b= e > 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. >=20 > I expected "server"-side vhost to be the same as "client" part (AKA virt= io), 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= . >=20 At this stage of release adding these changes is difficult as I don't have = knowledge on vhost. But at the same if anyone from committee would like to make these enhanceme= nts are welcome. Thanks, Reshma