From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: Benjamin LaHaise <bcrl@kvack.org>
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()
Date: Wed, 5 Oct 2016 14:58:12 -0300 [thread overview]
Message-ID: <737b5bf7-329e-c59d-7601-aea0f4ffbeab@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161005174146.GK23336@kvack.org>
Hi Benjamin,
On 10/05/2016 02:41 PM, Benjamin LaHaise wrote:
> 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.
Thanks for the suggestion.
Does the default also have implications other than memory usage?
For example, concurrency/performance of as much aio contexts running,
or if userspace could try to exploit some point with a larger number?
Wondering about it because it can be set based on num_possible_cpus(),
but that might be really large on high-end systems.
Regards,
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
next prev parent reply other threads:[~2016-10-05 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 22:55 aio: questions with ioctx_alloc() and large num_possible_cpus() Mauricio Faria de Oliveira
2016-10-05 6:34 ` Kent Overstreet
2016-10-05 17:21 ` Mauricio Faria de Oliveira
2016-10-05 17:41 ` Benjamin LaHaise
2016-10-05 17:58 ` Mauricio Faria de Oliveira [this message]
2016-10-05 18:17 ` Benjamin LaHaise
2016-10-05 19:22 ` Mauricio Faria de Oliveira
2016-10-28 18:59 ` Jeff Moyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=737b5bf7-329e-c59d-7601-aea0f4ffbeab@linux.vnet.ibm.com \
--to=mauricfo@linux.vnet.ibm.com \
--cc=bcrl@kvack.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).