From: Alexey Dobriyan <adobriyan@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] Bump vm.mmap_min_addr on 64-bit
Date: Tue, 2 Apr 2019 08:57:11 +0300 [thread overview]
Message-ID: <20190402055711.GA3078@avx2> (raw)
In-Reply-To: <20190401160559.6e945d8d235ae16006702bfc@linux-foundation.org>
On Mon, Apr 01, 2019 at 04:05:59PM -0700, Andrew Morton wrote:
> On Mon, 1 Apr 2019 08:06:13 +0300 Alexey Dobriyan <adobriyan@gmail.com> wrote:
>
> > No self respecting 64-bit program should ever touch that lowly 32-bit
> > part of address space.
> Gee. Do we have any idea what effect this will have upon all userspace
> programs, some of which do inexplicably weird things?
>
> What's the benefit?
Note the date :^)
prev parent reply other threads:[~2019-04-02 5:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 5:06 Alexey Dobriyan
2019-04-01 23:05 ` Andrew Morton
2019-04-02 5:57 ` Alexey Dobriyan [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=20190402055711.GA3078@avx2 \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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