user/sven/linux.git/lib/test_rhashtable.c, branch v4.4.63

rhashtable-test: extend to test concurrency

2015-08-17T21:33:47Z

After having tested insertion, lookup, table walk and removal, spawn a number of threads running operations on the same rhashtable. Each of them will: 1) insert it's own set of objects, 2) lookup every successfully inserted object and finally 3) remove objects in several rounds until all of them have been removed, making sure the remaining ones are still found after each round. This should put a good amount of load onto the system and due to synchronising thread startup via two semaphores also extensive concurrent table access. The default number of ten threads returned within half a second on my local VM with two cores. Running 200 threads took about four seconds. If slow systems suffer too much from this though, the default could be lowered or even set to zero so this extended test does not run at all by default. Signed-off-by: Phil Sutter Acked-by: Thomas Graf Signed-off-by: David S. Miller

rhashtable: Allow other tasks to be scheduled in large lookup loops

2015-07-21T07:10:08Z

Depending on system speed, the large lookup/insert/delete loops of the testsuite can take a considerable amount of time to complete causing watchdog warnings to appear. Allow other tasks to be scheduled throughout the loops. Reported-by: Meelis Roos Signed-off-by: Thomas Graf Acked-by: Eric Dumazet Signed-off-by: David S. Miller

rhashtable-test: Fix 64bit division

2015-05-05T23:30:47Z

A 64bit division went in unnoticed. Use do_div() to accomodate non 64bit architectures. Reported-by: kbuild test robot Fixes: 1aa661f5c3df ("rhashtable-test: Measure time to insert, remove & traverse entries") Signed-off-by: Thomas Graf Signed-off-by: David S. Miller

rhashtable-test: Detect insertion failures

2015-05-04T03:08:54Z

Account for failed inserts due to memory pressure or EBUSY and ignore failed entries during the consistency check. Signed-off-by: Thomas Graf Signed-off-by: David S. Miller

rhashtable-test: Use walker to test bucket statistics

2015-05-04T03:08:54Z

As resizes may continue to run in the background, use walker to ensure we see all entries. Also print the encountered number of rehashes queued up while traversing. This may lead to warnings due to entries being seen multiple times. We consider them non-fatal. Signed-off-by: Thomas Graf Signed-off-by: David S. Miller

rhashtable-test: Do not allocate individual test objects

2015-05-04T03:08:54Z

By far the most expensive part of the selftest was the allocation of entries. Using a static array allows to measure the rhashtable operations. Signed-off-by: Thomas Graf Signed-off-by: David S. Miller

rhashtable-test: Get rid of ptr in test_obj structure

2015-05-04T03:08:54Z

This only blows up the size of the test structure for no gain in test coverage. Reduces size of test_obj from 24 to 16 bytes. Signed-off-by: Thomas Graf Signed-off-by: David S. Miller

rhashtable-test: Measure time to insert, remove & traverse entries

2015-05-04T03:08:53Z

Make test configurable by allowing to specify all relevant knobs through module parameters. Do several test runs and measure the average time it takes to insert & remove all entries. Note, a deferred resize might still continue to run in the background. Signed-off-by: Thomas Graf Signed-off-by: David S. Miller

rhashtable-test: Remove unused TEST_NEXPANDS

2015-05-04T03:08:53Z

Signed-off-by: Thomas Graf Signed-off-by: David S. Miller

test_rhashtable: Remove bogus max_size setting

2015-04-03T19:09:36Z

Now that resizing is completely automatic, we need to remove the max_size setting or the test will fail. Reported-by: Fengguang Wu Signed-off-by: Herbert Xu Acked-by: Thomas Graf Signed-off-by: David S. Miller