From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f43.google.com (mail-oi0-f43.google.com [209.85.218.43]) by dpdk.org (Postfix) with ESMTP id 710C13775 for ; Wed, 13 May 2015 22:07:04 +0200 (CEST) Received: by oign205 with SMTP id n205so40268106oig.2 for ; Wed, 13 May 2015 13:07:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vqItnnCoZwzS6mbTOzEus48danhVXjDUD+MeM4j0hNk=; b=aiv8rPNWtGtq4o/u/CyjXWyxcgXVcuMvW+MgYWAQiFE+1qAPkeVA5Ajd3f/EZ8MYuv 8zrGdcibtWSN813Ulo72r/Sv5bWTSJcCnX4/HlLtzhfB0BUPgd6SpR8FpNkzbM78yY6B pq4O7kK/p7XOZ0YZIYXd9H//GU1B2jEmlHRpu4XEHIMC5o5N2h6M2i4rF3DO8ddtvn1i W/CQdiXTACxzEQWnONxJJBdVxkyfQKacTHwWmBh71naYcwy51IlLdNoVHnsI7I+ZWsYz aHLPofiBAspv2uyUxGG94+keZ1P+LLF/H6eE/VxjAcl+b/OUVhn2R9PsWHd3hKLopXyX OrxQ== MIME-Version: 1.0 X-Received: by 10.202.54.3 with SMTP id d3mr456241oia.103.1431547623994; Wed, 13 May 2015 13:07:03 -0700 (PDT) Received: by 10.202.179.195 with HTTP; Wed, 13 May 2015 13:07:03 -0700 (PDT) In-Reply-To: References: <1431119946-32078-1-git-send-email-rkerur@gmail.com> <1431119989-32124-1-git-send-email-rkerur@gmail.com> <2601191342CEEE43887BDE71AB9772582142E106@irsmsx105.ger.corp.intel.com> <2601191342CEEE43887BDE71AB9772582142E44A@irsmsx105.ger.corp.intel.com> <2601191342CEEE43887BDE71AB9772582142E475@irsmsx105.ger.corp.intel.com> Date: Wed, 13 May 2015 13:07:03 -0700 Message-ID: From: Ravi Kerur To: Jay Rolette Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" , Don Provan Subject: Re: [dpdk-dev] [PATCH v2] Implement memcmp using AVX/SSE instructions. 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: Wed, 13 May 2015 20:07:04 -0000 On Wed, May 13, 2015 at 5:21 AM, Jay Rolette wrote: > On Tue, May 12, 2015 at 8:16 PM, Ravi Kerur wrote: > >> On Mon, May 11, 2015 at 3:29 PM, Don Provan wrote: >> >> > I probably shouldn't stick my nose into this, but I can't help myself. >> > >> > An experienced programmer will tend to ignore the documentation for >> > a routine named "blahblah_memcmp" and just assume it functions like >> > memcmp. Whether or not there's currently a use case in DPDK is >> > completely irrelevant because as soon as there *is* a use case, some >> > poor DPDK developer will try to use rte_memcmp for that and may or >> > may not have a test case that reveals their mistake. >> > >> >> In general I agree with you. However, comparison is a hit(equal) or >> miss(unequal) is generally the case in networking. I haven't seen cases >> where "less than" or "greater than" has mattered. >> > > It's useful when you need to make sure packets from both sides of a > conversation go to the same processing queue/thread. Instead of hashing the > 5-tuple from the packet as src.ip, dst.ip, src.dport, dst.dport, etc., you > can use lesser.ip, higher.ip, lesser.sport, higher.dport, etc. > > Very common when you are doing deep packet inspection. > Thanks for sharing this information. > > Jay >