From: Cyril Hrubis <chrubis@suse.cz>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Michal Hocko <mhocko@kernel.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>,
linux-api@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org, Jann Horn <jannh@google.com>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v2] mmap.2: MAP_FIXED updated documentation
Date: Wed, 6 Dec 2017 11:01:18 +0100 [thread overview]
Message-ID: <20171206100118.GA13979@rei> (raw)
In-Reply-To: <2cff594a-b481-269d-dd91-ff2cc2f4100a@nvidia.com>
Hi!
> (It does seem unfortunate that the man page cannot help the programmer
> actually write correct code here. He or she is forced to read the kernel
> implementation, in order to figure out the true alignment rules. I was
> hoping we could avoid that.)
It would be nice if we had this information exported somehere so that we
do not have to rely on per-architecture ifdefs.
What about adding MapAligment or something similar to the /proc/meminfo?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-12-06 10:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 2:14 [PATCH v2] mmap.2: MAP_FIXED updated documentation john.hubbard
2017-12-04 10:55 ` Cyril Hrubis
2017-12-05 2:14 ` John Hubbard
2017-12-05 7:05 ` Michal Hocko
2017-12-05 7:42 ` John Hubbard
2017-12-05 8:52 ` Michal Hocko
2017-12-06 10:01 ` Cyril Hrubis [this message]
2017-12-06 21:21 ` John Hubbard
2017-12-07 12:58 ` Cyril Hrubis
2017-12-07 14:02 ` Michal Hocko
2017-12-09 17:19 ` Pavel Machek
2017-12-10 7:44 ` John Hubbard
2017-12-04 11:31 ` Mike Rapoport
2017-12-05 2:52 ` John Hubbard
2017-12-05 7:08 ` Michal Hocko
2017-12-05 7:43 ` John Hubbard
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=20171206100118.GA13979@rei \
--to=chrubis@suse.cz \
--cc=jannh@google.com \
--cc=jhubbard@nvidia.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=mtk.manpages@gmail.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).