From: Jeff Moyer <jmoyer@redhat.com>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>,
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: Fri, 28 Oct 2016 14:59:40 -0400 [thread overview]
Message-ID: <x49twbw710j.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20161005181741.GL23336@kvack.org> (Benjamin LaHaise's message of "Wed, 5 Oct 2016 14:17:41 -0400")
Benjamin LaHaise <bcrl@kvack.org> writes:
> Today's high end systems are tomorrow's desktops... It probably makes
Well, to some degree I agree with you. >100 processor high end systems
have been around for a long time, but we still don't have those on the
desktop. ;-)
> 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 actually wrote a patch to do this back in 2007:
http://www.gossamer-threads.com/lists/linux/kernel/1043934
It used the mlock rlimit. I ultimately decided to rescind it, since
there were years of experience with the current tunable, and plenty of
documentation on it, too. We could put aio-max-nr on the deprecated
path, though, if folks want to go that route. Let me know and I can
investigate resurrecting that patch. Though I would like input on
whether a new rlimit is desired.
Cheers,
Jeff
prev parent reply other threads:[~2016-10-28 18:59 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
2016-10-28 18:59 ` Jeff Moyer [this message]
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=x49twbw710j.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.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=mauricfo@linux.vnet.ibm.com \
--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).