From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
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 <rfc822;linux-fsdevel@vger.kernel.org>);
        Wed, 5 Oct 2016 14:02:26 -0400
Date: Wed, 5 Oct 2016 13:41:46 -0400
From: Benjamin LaHaise <bcrl@kvack.org>
To: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
        Alexander Viro <viro@zeniv.linux.org.uk>,
        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: <db64a8f3-cd15-2ccc-e120-ba0466f811d0@linux.vnet.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <db64a8f3-cd15-2ccc-e120-ba0466f811d0@linux.vnet.ibm.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

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."