From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jay Rolette Subject: Re: [PATCH 0/4] DPDK memcpy optimization Date: Thu, 22 Jan 2015 07:29:17 -0600 Message-ID: References: <20150119130221.GB21790@hmsreliant.think-freely.org> <20150120151118.GD18449@hmsreliant.think-freely.org> <20150120161453.GA5316@bricha3-MOBL3> <54BF9D59.7070104@bisdn.de> <20150121130234.GB10756@bricha3-MOBL3> <54BFA7D5.7020106@bisdn.de> <20150121132620.GC10756@bricha3-MOBL3> <20150121114947.0753ae87@urahara> <20150121205404.GB32617@hmsreliant.think-freely.org> <53D2253B-DE20-486E-ADF0-DA02AAB1EF35@netgate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: "dev-VfR2kkLFssw@public.gmane.org" To: Luke Gorrie Return-path: In-Reply-To: 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 Thu, Jan 22, 2015 at 3:06 AM, Luke Gorrie wrote: Here is another thought: when is it time to start thinking of packet copy > as a cheap unit-time operation? > Pretty much never short of changes to memory architecture, IMO. Frankly, there are never enough cycles for deep packet inspection applications that need to run at/near line-rate. Don't waste any doing something you can avoid in the first place. Microseconds matter. Scaling up to 100GbE, nanoseconds matter. Jay