From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id AC62C5A0A for ; Mon, 21 Dec 2015 18:22:55 +0100 (CET) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 327F51EB; Mon, 21 Dec 2015 12:22:55 -0500 (EST) Date: Mon, 21 Dec 2015 12:22:55 -0500 From: Matthew Hall To: "Gray, Mark D" Message-ID: <20151221172255.GA14384@mhcomputing.net> References: <20151214223613.GC21163@mhcomputing.net> <20151216104502.GA10020@bricha3-MOBL3> <98CBD80474FA8B44BF855DF32C47DC358AF76F@smartserver.smartshare.dk> <20151216115611.GB10020@bricha3-MOBL3> <20151216181557.GA16963@mhcomputing.net> <20151221153945.GA12016@bricha3-MOBL3> <98CBD80474FA8B44BF855DF32C47DC358AF79A@smartserver.smartshare.dk> <738D45BC1F695740A983F43CFE1B7EA943943F49@IRSMSX108.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <738D45BC1F695740A983F43CFE1B7EA943943F49@IRSMSX108.ger.corp.intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "dev@dpdk.org" , Morten =?iso-8859-1?Q?Br=F8rup?= Subject: Re: [dpdk-dev] tcpdump support in DPDK 2.3 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, 21 Dec 2015 17:22:55 -0000 On Mon, Dec 21, 2015 at 04:17:26PM +0000, Gray, Mark D wrote: > Is tcpdump used in large production cloud environments? I would have > thought other less intrusive (and less manual) tools would be used? Isn't > that one of the benefits of SDN. tcpdump, tshark, wireshark, libpcap, etc. have been used every single place I ever worked, including in production under heavy load. This is because nobody wants to redo the library of many tens of thousands of hours of protocol dissectors. This is also why I am trying to point out what is required to get a solution that I am confident will really work when people are counting on it, which I am concerned the current proposals do not cover. Matthew.