Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752683AbbEZOhZ (ORCPT ); Tue, 26 May 2015 10:37:25 -0400 Received: from mout.kundenserver.de ([212.227.126.131]:52913 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751297AbbEZOhX (ORCPT ); Tue, 26 May 2015 10:37:23 -0400 From: Arnd Bergmann To: Catalin Marinas Cc: Jungseok Lee , Catalin Marinas , "barami97@gmail.com" , Will Deacon , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator Date: Tue, 26 May 2015 11:51:17 +0200 Message-ID: <3076059.95sGQMhV87@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <1CD6E4BA-95AF-420C-8270-6AAF783B6F60@foss.arm.com> References: <1432483340-23157-1-git-send-email-jungseoklee85@gmail.com> <5601369.jDWtB6nFJC@wuerfel> <1CD6E4BA-95AF-420C-8270-6AAF783B6F60@foss.arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:rx/a0K4FnmJ0Jln4mEOUXsuizQ4OS2GpuXgfmkwKeRQ2HhnxKi2 e/fWD8KQT8pXpuQzRIr0Lu/dWQIe4RDsqAeHeM5XCp5zRQaHuxkvg9vBGocbEwm5nlV7nAO 5nENx1WvKapCS52/V8LCpfwpEisOvowMMLvYN4CoJnEO88o0tPF5ULa+0ozpok9qk7xNdko 7A8p/vRTy/WtpDejwfF1g== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1022 Lines: 23 On Tuesday 26 May 2015 01:36:29 Catalin Marinas wrote: > > > There are a lot of workloads that would benefit from having lower > > per-thread memory cost. > > If we keep the 16KB stack, is there any advantage in a separate IRQ one (assuming > that we won't overflow 16KB)? It makes possible errors more reproducible: we already know that we need over 8kb for normal stacks based on Minchan's findings, and the chance that an interrupt happens at a time when the stack is the highest is very low, but that just makes the bug much harder to find if you ever run into it. If we overflow the stack (independent of its size) with a process stack by itself, it will always happen in the same call chain, not a combination of a call chain an a particularly bad interrupt. Arnd -- 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/