Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754628AbcJESC2 (ORCPT ); Wed, 5 Oct 2016 14:02:28 -0400 Received: from kanga.kvack.org ([205.233.56.17]:51749 "EHLO kanga.kvack.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752248AbcJESC0 (ORCPT ); Wed, 5 Oct 2016 14:02:26 -0400 X-Greylist: delayed 1234 seconds by postgrey-1.27 at vger.kernel.org; Wed, 05 Oct 2016 14:02:26 EDT Date: Wed, 5 Oct 2016 13:41:46 -0400 From: Benjamin LaHaise To: Mauricio Faria de Oliveira Cc: Kent Overstreet , Alexander Viro , linux-fsdevel@vger.kernel.org, linux-aio@kvack.org, linux-kernel@vger.kernel.org Subject: Re: aio: questions with ioctx_alloc() and large num_possible_cpus() Message-ID: <20161005174146.GK23336@kvack.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 458 Lines: 13 On Tue, Oct 04, 2016 at 07:55:12PM -0300, Mauricio Faria de Oliveira wrote: > Hi Benjamin, Kent, and others, > > Would you please comment / answer about this possible problem? > Any feedback is appreciated. I'd suggest increasing the default limit by changing how it is calculated. The current number came about 13 years ago when machines had orders of magnitude less RAM than they do today. -ben -- "Thought is the essence of where you are now."