From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@suse.com>,
Randy Dunlap <rdunlap@infradead.org>,
Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: [PATCH v4 0/3] docs/core-api: add memory allocation guide
Date: Fri, 14 Sep 2018 12:27:55 +0300 [thread overview]
Message-ID: <1536917278-31191-1-git-send-email-rppt@linux.vnet.ibm.com> (raw)
Hi,
As Vlastimil mentioned at [1], it would be nice to have some guide about
memory allocation. This set adds such guide that summarizes the "best
practices".
The changes from the RFC include additions and corrections from Michal and
Randy. I've also added markup to cross-reference the kernel-doc
documentation.
I've split the patch into three to separate labels addition to the exiting
files from the new contents.
v3 -> v4:
* make GFP_*USER* description less confusing
v2 -> v3:
* s/HW/hardware
[1] https://www.spinics.net/lists/netfilter-devel/msg55542.html
Mike Rapoport (3):
docs: core-api/gfp_mask-from-fs-io: add a label for cross-referencing
docs: core-api/mm-api: add a lable for GFP flags section
docs: core-api: add memory allocation guide
Documentation/core-api/gfp_mask-from-fs-io.rst | 2 +
Documentation/core-api/index.rst | 1 +
Documentation/core-api/memory-allocation.rst | 122 +++++++++++++++++++++++++
Documentation/core-api/mm-api.rst | 2 +
4 files changed, 127 insertions(+)
create mode 100644 Documentation/core-api/memory-allocation.rst
--
2.7.4
next reply other threads:[~2018-09-14 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 9:27 Mike Rapoport [this message]
2018-09-14 9:27 ` [PATCH v4 1/3] docs: core-api/gfp_mask-from-fs-io: add a label for cross-referencing Mike Rapoport
2018-09-14 9:27 ` [PATCH v4 2/3] docs: core-api/mm-api: add a lable for GFP flags section Mike Rapoport
2018-09-14 9:27 ` [PATCH v4 3/3] docs: core-api: add memory allocation guide Mike Rapoport
2018-09-20 4:29 ` [PATCH v4 0/3] docs/core-api: " Mike Rapoport
2018-09-20 17:04 ` Jonathan Corbet
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=1536917278-31191-1-git-send-email-rppt@linux.vnet.ibm.com \
--to=rppt@linux.vnet.ibm.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rdunlap@infradead.org \
--cc=vbabka@suse.cz \
--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).