Thanks for the comment Bruce, I agree with you. As I think about it, I believe the old scaling test can be removed since currently the multiwriter is supported inside the library, and we already have the multiwriter test.
I will post a V2 version of this patch series to remove that test. >-----Original Message----- >From: Richardson, Bruce >Sent: Wednesday, October 24, 2018 1:37 PM >To: Wang, Yipeng1 <yipeng1.w...@intel.com> >Cc: step...@networkplumber.org; dev@dpdk.org; honnappa.nagaraha...@arm.com; >Gobriel, Sameh <sameh.gobr...@intel.com> >Subject: Re: [PATCH v1 3/3] test/hash: add readwrite test for ext table > >On Wed, Oct 10, 2018 at 02:48:05PM -0700, Yipeng Wang wrote: >> This commit improves the readwrite test to consider extendable table >> feature and add more functional tests to cover more corner cases. >> >> Signed-off-by: Yipeng Wang <yipeng1.w...@intel.com> --- >> test/test/test_hash_readwrite.c | 70 >> ++++++++++++++++++++++++++++++++++------- 1 file changed, 58 >> insertions(+), 12 deletions(-) >> >With the extension of this test case, and the addition of other test cases >by Honnappa in the other patch sets in this release, we are building up >quite a large set of hash table autotests, some of whose meaning and use is >a bit obscure. Are there any hash tests that you feel could be removed at >this point, to simplify things? > >/Bruce
