From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH 0/4] DPDK memcpy optimization Date: Wed, 21 Jan 2015 16:53:17 -0800 Message-ID: <20150121165317.1bb03c3c@urahara> 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 Content-Transfer-Encoding: quoted-printable Cc: dev-VfR2kkLFssw@public.gmane.org To: Jim Thompson Return-path: In-Reply-To: <53D2253B-DE20-486E-ADF0-DA02AAB1EF35-jiyf0hk6h8BBDgjK7y7TUQ@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, 21 Jan 2015 15:25:40 -0600 Jim Thompson wrote: > I=E2=80=99m not as concerned with compile times given the potential perfo= rmance boost. Compile time matters. Right now full build of large project is fast. Like 2 minutes or less. Is this only the test applications (which can be disabled from the build), or the library trying to do some tests. Since the build and target environm= ent will be different on a real product, the whole scheme seems flawed.