From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-fw-4101.amazon.com (smtp-fw-4101.amazon.com [72.21.198.25]) by dpdk.org (Postfix) with ESMTP id 4E3A4333 for ; Tue, 23 Sep 2014 05:37:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1411443844; x=1442979844; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=VZ41VCSwzp5ujYzOCdKCHewSSiQZ+stEwDpqGmPVYA8=; b=k10Ia+FBQoHK4LASl4PZhHT/ilC3o0qh5I6WcQpCelITN+e4HMazFGXN PbGG+DW8DHSsO4CJbjqRE1XZEAb4h94AVnse3awmABFcYErTDRPzLPcV7 UPcBfRYWpA/fv2aScBJMVmx34V41D7dQG8sORg1i5RmkCP97ChKoonI67 g=; X-IronPort-AV: E=Sophos;i="5.04,577,1406592000"; d="scan'208";a="133816988" Received: from email-inbound-relay-60046.pdx1.amazon.com ([10.232.152.66]) by smtp-border-fw-out-4101.iad4.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Sep 2014 03:44:01 +0000 Received: from ex10-hub-9004.ant.amazon.com (pdx2-ws-svc-lb17-vlan3.amazon.com [10.247.140.70]) by email-inbound-relay-60046.pdx1.amazon.com (8.14.7/8.14.7) with ESMTP id s8N3i09h004367 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 23 Sep 2014 03:44:01 GMT Received: from EX10-MBX-9001.ant.amazon.com ([fe80::1023:3a45:4674:52c6]) by ex10-hub-9004.ant.amazon.com ([::1]) with mapi id 14.03.0181.006; Mon, 22 Sep 2014 20:44:00 -0700 From: "Saha, Avik (AWS)" To: Matthew Hall Thread-Topic: [dpdk-dev] LRU using DPDK 1.7 Thread-Index: Ac/Wyt0u/iX0G6X+Tj+qWWDaeZTa0gAPj/sAAApBnQA= Date: Tue, 23 Sep 2014 03:43:59 +0000 Message-ID: References: <20140923013356.GA26558@mhcomputing.net> In-Reply-To: <20140923013356.GA26558@mhcomputing.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.184.49.70] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] LRU using DPDK 1.7 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: Tue, 23 Sep 2014 03:37:57 -0000 So with DPDK 1.7 there are 2 separate implementations - one is the rte_hash= which does not support LRU (at least to my understanding - I could be wron= g here) and then there is the librte_table library which has support for LR= U in a hash table. I m a little confused as to which one you are referring = to Matthew. -----Original Message----- From: Matthew Hall [mailto:mhall@mhcomputing.net]=20 Sent: Monday, September 22, 2014 6:34 PM To: Saha, Avik (AWS) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] LRU using DPDK 1.7 On Tue, Sep 23, 2014 at 01:08:21AM +0000, Saha, Avik (AWS) wrote: > I was wondering if there is way to use the rte_table_hash_lru without=20 > building a pipeline - Basically using the same hash table like=20 > functionality of add, delete and lookup without setting up a pipeline=20 > and connect it to ports etc. I've been finding that rte_hash is designed only for some very specialized = purposes. It doesn't work well if you use unexpected sizes of keys or want = behavior that isn't precisely doing what the designers of the hash used it = for... it's not very general-purpose. I did try to point out one example of the issue but I didn't get much respo= nse yet to my questions about its limitations and whether a more general-pu= rpose table was available, or at least some discussion what rte_hash is for= and what it's not for. Matthew.