From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id CC15F1B213 for ; Thu, 27 Sep 2018 13:19:57 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Sep 2018 04:19:56 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,310,1534834800"; d="scan'208";a="83727724" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.107]) by FMSMGA003.fm.intel.com with SMTP; 27 Sep 2018 04:18:00 -0700 Received: by (sSMTP sendmail emulation); Thu, 27 Sep 2018 12:17:59 +0100 Date: Thu, 27 Sep 2018 12:17:59 +0100 From: Bruce Richardson To: Yipeng Wang Cc: dev@dpdk.org, honnappa.nagarahalli@arm.com, sameh.gobriel@intel.com Message-ID: <20180927111759.GD19604@bricha3-MOBL.ger.corp.intel.com> References: <1536253745-133104-1-git-send-email-yipeng1.wang@intel.com> <1537966465-248530-1-git-send-email-yipeng1.wang@intel.com> <1537966465-248530-2-git-send-email-yipeng1.wang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1537966465-248530-2-git-send-email-yipeng1.wang@intel.com> Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.10.1 (2018-07-13) Subject: Re: [dpdk-dev] [PATCH v3 1/5] test/hash: fix bucket size in hash perf test X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2018 11:19:58 -0000 On Wed, Sep 26, 2018 at 05:54:21AM -0700, Yipeng Wang wrote: > The bucket size was changed from 4 to 8 but the corresponding > perf test was not changed accordingly. > > In the test, the bucket size and number of buckets are used > to map to the underneath rte_hash structure. They are used > to test performance of two conditions: keys in primary > buckets only and keys in both primary and secondary buckets. > > Although there is no functional issue with bucket size set > to 4, it mismatches the underneath rte_hash structure, > which may affect code readability and future extension. > > Fixes: 58017c98ed53 ("hash: add vectorized comparison") > Cc: stable@dpdk.org > > Signed-off-by: Yipeng Wang > --- > test/test/test_hash_perf.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/test/test/test_hash_perf.c b/test/test/test_hash_perf.c > index 33dcb9f..9ed7125 100644 > --- a/test/test/test_hash_perf.c > +++ b/test/test/test_hash_perf.c > @@ -20,7 +20,7 @@ > #define MAX_ENTRIES (1 << 19) > #define KEYS_TO_ADD (MAX_ENTRIES * 3 / 4) /* 75% table utilization */ > #define NUM_LOOKUPS (KEYS_TO_ADD * 5) /* Loop among keys added, several times */ > -#define BUCKET_SIZE 4 > +#define BUCKET_SIZE 8 > #define NUM_BUCKETS (MAX_ENTRIES / BUCKET_SIZE) > #define MAX_KEYSIZE 64 > #define NUM_KEYSIZES 10 Honnappa's suggestion that a comment be added here to indicate that the value should be kept in sync with the rte_hash one is a good one, and should be done. Otherwise: Acked-by: Bruce Richardson > -- > 2.7.4 >