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 1DD488D99 for ; Tue, 1 Dec 2015 20:28:05 +0100 (CET) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 8BA271BB; Tue, 1 Dec 2015 14:28:04 -0500 (EST) Date: Tue, 1 Dec 2015 14:28:04 -0500 From: Matthew Hall To: Kyle Larose Message-ID: <20151201192804.GA28164@mhcomputing.net> References: <20151130171655.70e4ce25@xeon-e3> <20151201100333.GA32252@bricha3-MOBL3> <20151201.202639.45956937.shin@lenovo> <20151201115816.GA29824@bricha3-MOBL3> <20151201134228.GA21396@mhcomputing.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] 2.3 Roadmap 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, 01 Dec 2015 19:28:05 -0000 On Tue, Dec 01, 2015 at 09:45:56AM -0500, Kyle Larose wrote: > Earlier Stephen mentioned using the named pipe behaviour of tcpdump. > Is there an opportunity to take what you have mentioned here and marry > it to the named pipe output to get the perf you need? I am wondering about the same thing. But I didn't want to limit the scope of solutions too much so I didn't specifically enumerate this possibility. Matthew.