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 A7A61C3A6 for ; Thu, 18 Feb 2016 15:08:18 +0100 (CET) Received: from eucpsbgm1.samsung.com (unknown [203.254.199.244]) by mailout3.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0O2Q00IM5XXTO1A0@mailout3.w1.samsung.com> for dev@dpdk.org; Thu, 18 Feb 2016 14:08:17 +0000 (GMT) X-AuditID: cbfec7f4-f79026d00000418a-08-56c5d051536c Received: from eusync4.samsung.com ( [203.254.199.214]) by eucpsbgm1.samsung.com (EUCPMTA) with SMTP id 50.3A.16778.150D5C65; Thu, 18 Feb 2016 14:08:17 +0000 (GMT) Received: from fedinw7x64 ([106.109.131.169]) by eusync4.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTPA id <0O2Q005WRXXS95A0@eusync4.samsung.com>; Thu, 18 Feb 2016 14:08:17 +0000 (GMT) From: Pavel Fedin To: 'Reshma Pattan' , dev@dpdk.org References: <1455289045-25915-1-git-send-email-reshma.pattan@intel.com> In-reply-to: <1455289045-25915-1-git-send-email-reshma.pattan@intel.com> Date: Thu, 18 Feb 2016 17:08:16 +0300 Message-id: <014201d16a55$d05e4b20$711ae160$@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: AQIv6L0UmHAJ53r3gd8NJkyOKRJNh5501mgQ Content-language: ru X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLLMWRmVeSWpSXmKPExsVy+t/xa7qBF46GGdyfLGzx7tN2JovlX2aw ODB5/FqwlNVj8Z6XTAFMUVw2Kak5mWWpRfp2CVwZry9+YCv4z1Vx+uhS9gbGHxxdjJwcEgIm Ete7prFD2GISF+6tZ+ti5OIQEljKKNHwaBqU851RYsGqYywgVWwC6hKnv34As0UErCWW7DjF DGILCbhLtF7ewwpicwp4SHx8vRvMFhYIkVg0fw4TiM0ioCrx9fQbNhCbV8BS4vzLPnYIW1Di x+R7YDOZBbQk1u88zgRhy0tsXvOWGeI6BYkdZ18zQuw1klg7bw8bRI2IxLR/95gnMArOQjJq FpJRs5CMmoWkZQEjyypG0dTS5ILipPRcQ73ixNzi0rx0veT83E2MkED+soNx8TGrQ4wCHIxK PLwcr4+ECbEmlhVX5h5ilOBgVhLh3b33aJgQb0piZVVqUX58UWlOavEhRmkOFiVx3rm73ocI CaQnlqRmp6YWpBbBZJk4OKUaGC0CCrZZpab/OjX31Bet38oqVfM5ljuckNMUUaz7U2y579Fx cb27r+wVlAyXHHLROMMY2T7p2W21FI/WxuQfdg+OpBnvaMz0PL9yB1+e262o2Tbejm/0T//X FXp15kO84KKDL7rDZCt/CfDFXJ4am3332rcZyTaSd+qW2/RUn7rsLc1m3yhdpsRSnJFoqMVc VJwIAPfVGsFgAgAA 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: Thu, 18 Feb 2016 14:08:18 -0000 Hello! With the aforementioned fix (disabling src_ip_filter if zero) i've got the patch series working. Now i have some more notes on usability: > 2)Start proc_info(runs as secondary process by default)application with new parameters for > tcpdump. > ex: sudo ./build/app/proc_info/dpdk_proc_info -c 0x4 -n 2 -- -p 0x3 --tcpdump '(0,0)(1,0)' -- > src-ip-filter="2.2.2.2" 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 through 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? 2. What if i don't want separate RX and TX streams either? It only prevents me from seeing the complete picture. 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. 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. Kind regards, Pavel Fedin Senior Engineer Samsung Electronics Research center Russia