From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: [PATCH RFC] librte_reorder: new reorder library Date: Wed, 8 Oct 2014 16:07:28 -0700 Message-ID: <20141008230728.GA29712@mhcomputing.net> References: <3AEA2BF9852C6F48A459DA490692831FE21954@IRSMSX109.ger.corp.intel.com> <20141008224111.GC29243@mhcomputing.net> <20141008225540.GA15850@hmsreliant.think-freely.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev-VfR2kkLFssw@public.gmane.org" To: Neil Horman Return-path: Content-Disposition: inline In-Reply-To: <20141008225540.GA15850-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Wed, Oct 08, 2014 at 06:55:41PM -0400, Neil Horman wrote: > I think because there is a possibility that multiple workers may be used for a > single tx queue. > > Neil OK, so, in my application packets are RX'ed to a predictable RX queue and core using RSS. Then you put them into a predictable TX queue for the same core, in the same order they came in from the RX queue with RSS enabled. So you've got a consistent-hashed subset of packets as input, being converted to output in the same order. Will it work, or not work? I'm just curious if my app is doing it wrong and I need to fix it, or how this case should be handled in general... Matthew.