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 16:22:02 -0300 [thread overview]
Message-ID: <a2a7cac6-30dd-7d73-6a0a-5cd602a01b33@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161005181741.GL23336@kvack.org>
Ben,
On 10/05/2016 03:17 PM, Benjamin LaHaise wrote:
> Anything's possible when a local user can run code. [snip] That
> said, local users tend not to DoS themselves.
Agree. I thought of something that could be particularly related to
the aio implementation; but I guess there's nothing so special then.
> [snip] It probably makes
> sense to implement per-user limits rather than the current global limit,
> and maybe even convert them to an rlimit to better fit in with the
> available frameworks for managing these things.
I see it would be a nice improvement, but unfortunately that's not a
task that I can take at the moment. For now, the most I'm able to do
is to continue to try to understand whether there's something we can
do that may help the small nr_events case to be more on par with the
large nr_events case.. or any other beginner-level fixes to the area. :)
Thanks again,
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
next prev parent reply other threads:[~2016-10-05 19:23 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
2016-10-05 18:17 ` Benjamin LaHaise
2016-10-05 19:22 ` Mauricio Faria de Oliveira [this message]
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=a2a7cac6-30dd-7d73-6a0a-5cd602a01b33@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).