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 097002BFD for ; Tue, 23 Feb 2016 14:16:45 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 23 Feb 2016 05:16:44 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,489,1449561600"; d="scan'208";a="919287752" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by orsmga002.jf.intel.com with ESMTP; 23 Feb 2016 05:16:43 -0800 Received: from irsmsx109.ger.corp.intel.com ([169.254.13.100]) by IRSMSX153.ger.corp.intel.com ([169.254.9.60]) with mapi id 14.03.0248.002; Tue, 23 Feb 2016 13:16:41 +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/E2nk2UFTSFmQ58x4FMAgAfJAmA= Date: Tue, 23 Feb 2016 13:16:40 +0000 Message-ID: <3AEA2BF9852C6F48A459DA490692831FFC6353@IRSMSX109.ger.corp.intel.com> References: <1455289045-25915-1-git-send-email-reshma.pattan@intel.com> <014201d16a55$d05e4b20$711ae160$@samsung.com> In-Reply-To: <014201d16a55$d05e4b20$711ae160$@samsung.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYjUwODVmZGYtOGI4OC00ZTQ5LTkyZWMtNDkxN2Q1NzQ4ODM1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IiszUjJQejQ0U05KbHp3ditJZkU1MVlUNTFEb1RDcnIycUp6YlJWUm5RTE09In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.181] 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: Tue, 23 Feb 2016 13:16:46 -0000 Hi, > -----Original Message----- > From: Pavel Fedin [mailto:p.fedin@samsung.com] > Sent: Thursday, February 18, 2016 2:08 PM > To: Pattan, Reshma ; dev@dpdk.org > Subject: RE: [dpdk-dev] [PATCH v2 0/5] add dpdk packet capture support fo= r > tcpdump >=20 >=20 > 1. Perhaps, ability to separate queues is useful for something. But not = always. > For example, what if i want to capture all the traffic which passes throu= gh some > interface (common use case)? For example, with OpenVSwitch i can have 9 > queues on my networking card. So, i have to enumerate all of them: > (0,0)(0,1)(0,2)... It's insane and inconvenient with many queues. What if= you > could have shorthand notation, like (0) or (0,*) for this? I will fix this in my next version of patch. > 2. What if i don't want separate RX and TX streams either? It only preve= nts me > from seeing the complete picture. Do you mean not to have separate pcap files for tx and rx? If so, I would p= refer to keep this as it is. Because pcap changes need to be replaced with TUN/TAP pmd once available in= future.=20 > 3. vhostuser ports are missing. Perhaps not really related to this patch= set, i just > don't know how much code "server" part of vhostuser shares with normal PM= Ds, > but anyway, ability to dump them too would be nice to have. >=20 I think this can be done in future i.e. when vhost as PMD is available. But= as of now vhost is library. > Not directly related, but could we have some interface to tcpdump or > wireshark? Would be good to have ability to dump packets in real time. This can be done in future once KNI or TUN/TAP PMDs is available in DPDK. Thanks, Reshma