Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751969AbaFDTIt (ORCPT ); Wed, 4 Jun 2014 15:08:49 -0400 Received: from e37.co.us.ibm.com ([32.97.110.158]:50248 "EHLO e37.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751747AbaFDTIq (ORCPT ); Wed, 4 Jun 2014 15:08:46 -0400 From: Jack Miller To: linux-kernel@vger.kernel.org Cc: mikey@au1.ibm.com, anton@au1.ibm.com, miltonm@us.ibm.com Subject: shm: shm_exit scalability fixes Date: Wed, 4 Jun 2014 14:07:45 -0500 Message-Id: <1401908868-14554-1-git-send-email-millerjo@us.ibm.com> X-Mailer: git-send-email 1.9.1 X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 14060419-7164-0000-0000-0000023A41A1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org All - This is small set of patches our team has had kicking around for a few versions internally that fixes tasks getting hung on shm_exit when there are many threads hammering it at once. Anton wrote a simple test to cause the issue: http://ozlabs.org/~anton/junkcode/bust_shm_exit.c Before applying this patchset, this test code will cause either hanging tracebacks or pthread out of memory errors. After this patchset, it will still produce output like: root@somehost:~# ./bust_shm_exit 1024 160 ... INFO: rcu_sched detected stalls on CPUs/tasks: {} (detected by 116, t=2111 jiffies, g=241, c=240, q=7113) INFO: Stall ended before state dump start ... But the task will continue to run along happily, so we consider this an improvement over hanging, even if it's a bit noisy. I didn't author these patches, but I'd be happy to take any feedback and address any issues. - Jack -- 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/