From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by dpdk.org (Postfix) with ESMTP id E29C95927 for ; Thu, 23 Apr 2015 10:21:16 +0200 (CEST) Received: by wizk4 with SMTP id k4so206613957wiz.1 for ; Thu, 23 Apr 2015 01:21:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=51h9T2rINiyfAvI9rNJcNc860/67yv66WTYhK5q+I+Q=; b=mlq+V7i8S61bDkF7Fc2/7M+GaEKLaAzM6u00lkLzv3FClILQABPi/invz2h7/Riukc ko+baeeXHR83hiHBlTZIS/9oGVk21zOh8rFLj4tfwnhfPuAsxtaK4JoxAqKcbXImLU0P 3abvJGMokffmRWDU0W4v1kghnShxnOd8FFGlrs2oNisfLRxRqMIC61HT2eXyzI0FX25K rcZv1ogRYAltLMfg9mkoe836A7aZ2dNeWmINcBQM+03KnRoWssUlgnJC9XkjP3tiKn35 odX5kyH5fDYiIKWLlb2nu+dv5uYjNgHzMslX8ijdAQwOeiM5Za2SCL48iQKb1T9ECHYE KJjA== MIME-Version: 1.0 X-Received: by 10.194.200.42 with SMTP id jp10mr3068045wjc.66.1429777276765; Thu, 23 Apr 2015 01:21:16 -0700 (PDT) Sender: lukego@gmail.com Received: by 10.27.134.198 with HTTP; Thu, 23 Apr 2015 01:21:16 -0700 (PDT) In-Reply-To: <20150423081138.GA8592@bricha3-MOBL3> References: <1429716828-19012-1-git-send-email-rkerur@gmail.com> <1429716828-19012-2-git-send-email-rkerur@gmail.com> <55389E44.8030603@intel.com> <20150423081138.GA8592@bricha3-MOBL3> Date: Thu, 23 Apr 2015 10:21:16 +0200 X-Google-Sender-Auth: LN8COJNsGjObJ21YgHHijVC_Rjg Message-ID: From: Luke Gorrie To: Bruce Richardson Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH] Implement memcmp using AVX/SSE instructio 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: Thu, 23 Apr 2015 08:21:17 -0000 On 23 April 2015 at 10:11, Bruce Richardson wrote: > Also, if I read your quoted performance numbers in your earlier mail > correctly, > we are only looking at a 1-4% performance increase. Is the additional code > to > maintain worth the benefit? > ... and if so, how would one decide whether it is better to to add this to DPDK vs contribute it to GNU libc? Pawel noted that this is not compatible with memcmp(3). It is very similar to the legacy function bcmp(3) though so perhaps libc would accept it as such. Cheers, -Luke