From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-fw-9102.amazon.com (smtp-fw-9102.amazon.com [207.171.184.29]) by dpdk.org (Postfix) with ESMTP id 74D2E1F5 for ; Thu, 25 Sep 2014 01:06:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1411600381; x=1443136381; h=from:to:subject:date:message-id:mime-version; bh=xsfPtcj0/ZFfF3AmAfAzGW6KHUIS1l/bsJAIrjvDV4Q=; b=c8PYXaJrU8LbxOdRanDkUSRuBDF7puMlTpzh3koDw1f1yzKarqdVJJlG To1IxM0h4gFN1VRov0GMuZouiDGDQjthNv/p7M0VPYFenp1xFzs+EHwsr NIiD4rXrRIAogLRVnQzS+WzfFpyM4t3bvtnS+JhN7uH+Hvm0QBfbcqMNH Q=; X-IronPort-AV: E=Sophos;i="5.04,591,1406592000"; d="scan'208,217";a="147836128" Received: from email-inbound-relay-64002.pdx4.amazon.com ([10.220.169.156]) by smtp-border-fw-out-9102.sea19.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Sep 2014 23:12:56 +0000 Received: from ex10-hub-31002.ant.amazon.com (pdx2-ws-svc-lb17-vlan2.amazon.com [10.247.140.66]) by email-inbound-relay-64002.pdx4.amazon.com (8.14.7/8.14.7) with ESMTP id s8ONCufN016503 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for ; Wed, 24 Sep 2014 23:12:56 GMT Received: from EX10-MBX-9001.ant.amazon.com ([fe80::1023:3a45:4674:52c6]) by ex10-hub-31002.ant.amazon.com ([::1]) with mapi id 14.03.0181.006; Wed, 24 Sep 2014 16:12:14 -0700 From: "Saha, Avik (AWS)" To: "dev@dpdk.org" Thread-Topic: Strange behaviour with LRU table Thread-Index: Ac/YSboptL/a02EkT9uykaJpHUzkqQ== Date: Wed, 24 Sep 2014 23:12:13 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.184.49.70] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Strange behaviour with LRU table 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, 24 Sep 2014 23:06:47 -0000 1) All the calls to add entries succeeds 2) The key look up works as expected. 3) The value (entry_data) that is returned is incorrect for every othe= r entry - 1st entry data on .f_action_hit is wrong, 2nd entry_data on .f_a= ction_hit is correct and so on. I have initialized my LRU as follows: struct rte_pipeline_table_params table_params =3D { .ops =3D &rte_table_hash_lru_dosig_ops, .arg_create =3D &rule_tbl_params, .f_action_hit =3D rw_pipeline_stage_2_cache_hit, .f_action_miss =3D rw_pipeline_stage_2_cache_miss, .arg_ah =3D (void *)lcore_params, .action_data_size =3D 16, }; Is there something obvious I am missing - from first look it seems to be a = problem with cache lines but I really am not sure. Avik