Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752018AbbHPPCs (ORCPT ); Sun, 16 Aug 2015 11:02:48 -0400 Received: from mail-wi0-f177.google.com ([209.85.212.177]:35804 "EHLO mail-wi0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751959AbbHPPCr (ORCPT ); Sun, 16 Aug 2015 11:02:47 -0400 Date: Sun, 16 Aug 2015 17:02:44 +0200 From: Thomas Graf To: Phil Sutter Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, davem@davemloft.net Subject: Re: [PATCH] rhashtable-test: extend to test concurrency Message-ID: <20150816150244.GA6844@pox.localdomain> References: <1439591835-30357-1-git-send-email-phil@nwl.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1439591835-30357-1-git-send-email-phil@nwl.cc> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1307 Lines: 30 On 08/15/15 at 12:37am, Phil Sutter wrote: > 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 Looks great. A default of 10 makes sense as well. Thanks a lot! Acked-by: Thomas Graf -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/