From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752980AbdGYQkF (ORCPT ); Tue, 25 Jul 2017 12:40:05 -0400 Received: from mail-qk0-f179.google.com ([209.85.220.179]:36069 "EHLO mail-qk0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752938AbdGYQkB (ORCPT ); Tue, 25 Jul 2017 12:40:01 -0400 Date: Tue, 25 Jul 2017 12:39:57 -0400 From: Tejun Heo To: Michael Ellerman Cc: Michal Hocko , Jiri Kosina , linux-mm@kvack.org, LKML Subject: Re: pcpu allocator on large NUMA machines Message-ID: <20170725163957.GA3216015@devbig577.frc2.facebook.com> References: <20170724134240.GL25221@dhcp22.suse.cz> <20170724135714.GA3240919@devbig577.frc2.facebook.com> <20170724142826.GN25221@dhcp22.suse.cz> <877eyxz4r8.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <877eyxz4r8.fsf@concordia.ellerman.id.au> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Michael. On Tue, Jul 25, 2017 at 11:26:03AM +1000, Michael Ellerman wrote: > I don't think we want to stop using embed first chunk unless we have to. > > We have code that accesses percpu variables in real mode (with the MMU > off), and that wouldn't work easily if the first chunk wasn't in the > linear mapping. So it's not just an optimisation for us. > > We can fairly easily make the vmalloc space 56T, and I'm working on a > patch to make it ~500T on newer machines. Yeah, the only constraint is the size of vmalloc area in relation to the maximum spread across NUMA regions. If the vmalloc space can be made bigger, that'd be the best option. As the area percpu allocator actually uses is very small comparatively, it doesn't have to be a lot larger either. Thanks. -- tejun