From: Andy Lutomirski <luto@amacapital.net>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Christopher Covington <cov@codeaurora.org>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
Linaro Dev Mailman List <linaro-dev@lists.linaro.org>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
Mark Brown <broonie@linaro.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Dmitry Safonov <dsafonov@virtuozzo.com>
Subject: Re: JITs and 52-bit VA
Date: Wed, 22 Jun 2016 13:46:18 -0700 [thread overview]
Message-ID: <CALCETrULT6Kp_sA4+3=MgFoS0WSzfCmzPvk8dj89raqLC86XKw@mail.gmail.com> (raw)
In-Reply-To: <20160622194425.GB2045@uranus.lan>
On Wed, Jun 22, 2016 at 12:44 PM, Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> On Wed, Jun 22, 2016 at 12:20:13PM -0700, Andy Lutomirski wrote:
>> >>
>> >> As an example, a 32-bit x86 program really could have something mapped
>> >> above the 32-bit boundary. It just wouldn't be useful, but the kernel
>> >> should still understand that it's *user* memory.
>> >>
>> >> So you'd have PR_SET_MMAP_LIMIT and PR_GET_MMAP_LIMIT or similar instead.
>> >
>> > +1. Also it might be (not sure though, just guessing) suitable to do such
>> > thing via memory cgroup controller, instead of carrying this limit per
>> > each process (or task structure/vma or mm).
>>
>> I think we'll want this per mm. After all, a high-VA-limit-aware bash
>> should be able run high-VA-unaware programs without fiddling with
>> cgroups.
>
> Wait. You mean to have some flag in mm struct and consider
> its value on mmap call?
Exactly.
--Andy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-06-22 20:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A8E6E6D-6CF7-4964-A62E-467AE287D415@linaro.org>
2016-06-22 14:53 ` Christopher Covington
2016-06-22 15:13 ` Andy Lutomirski
2016-06-22 19:18 ` Cyrill Gorcunov
2016-06-22 19:20 ` Andy Lutomirski
2016-06-22 19:44 ` Cyrill Gorcunov
2016-06-22 20:46 ` Andy Lutomirski [this message]
2016-06-22 21:38 ` Cyrill Gorcunov
2016-06-22 19:56 ` Dave Hansen
2016-06-22 20:10 ` Cyrill Gorcunov
2016-06-22 20:17 ` Cyrill Gorcunov
2016-06-22 20:24 ` Kirill A. Shutemov
2016-06-22 20:41 ` Dave Hansen
2016-06-22 21:06 ` Cyrill Gorcunov
2016-06-23 8:20 ` Dmitry Safonov
2016-06-22 15:40 ` Kirill A. Shutemov
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='CALCETrULT6Kp_sA4+3=MgFoS0WSzfCmzPvk8dj89raqLC86XKw@mail.gmail.com' \
--to=luto@amacapital.net \
--cc=arnd.bergmann@linaro.org \
--cc=broonie@linaro.org \
--cc=cov@codeaurora.org \
--cc=dsafonov@virtuozzo.com \
--cc=gorcunov@gmail.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-mm@kvack.org \
--cc=maxim.kuvyrkov@linaro.org \
/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