From: "Sean O. Stalley" <sean.stalley@intel.com>
To: corbet@lwn.net, vinod.koul@intel.com, bhelgaas@google.com,
Julia.Lawall@lip6.fr, Gilles.Muller@lip6.fr,
nicolas.palix@imag.fr, mmarek@suse.cz, akpm@linux-foundation.org
Cc: sean.stalley@intel.com, bigeasy@linutronix.de,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, linux-pci@vger.kernel.org,
linux-mm@kvack.org, cocci@systeme.lip6.fr
Subject: [PATCH v2 0/4] mm: add dma_pool_zalloc() & pci_pool_zalloc()
Date: Fri, 31 Jul 2015 12:36:40 -0700 [thread overview]
Message-ID: <1438371404-3219-1-git-send-email-sean.stalley@intel.com> (raw)
Currently a call to dma_pool_alloc() with a ___GFP_ZERO flag returns
a non-zeroed memory region.
This patchset adds support for the __GFP_ZERO flag to dma_pool_alloc(),
adds 2 wrapper functions for allocing zeroed memory from a pool,
and provides a coccinelle script for finding & replacing instances of
dma_pool_alloc() followed by memset(0) with a single dma_pool_zalloc() call.
Changes from v1 to v2:
- don't memset() POOL_POISON_ALLOCATED in dma_pool_alloc() if
__GFP_ZERO is set
- Ran test to see how often pool_alloc_page() is called
There was some concern that this always calls memset() to zero,
instead of passing __GFP_ZERO into the page allocator.
[https://lkml.org/lkml/2015/7/15/881]
I ran a test on my system to get an idea of how often dma_pool_alloc()
calls into pool_alloc_page().
After Boot: [ 30.119863] alloc_calls:541, page_allocs:7
After an hour: [ 3600.951031] alloc_calls:9566, page_allocs:12
After copying 1GB file onto a USB drive:
[ 4260.657148] alloc_calls:17225, page_allocs:12
It doesn't look like dma_pool_alloc() calls down to the page allocator
very often (at least on my system).
Sean O. Stalley (4):
mm: Add support for __GFP_ZERO flag to dma_pool_alloc()
mm: Add dma_pool_zalloc() call to DMA API
pci: mm: Add pci_pool_zalloc() call
coccinelle: mm: scripts/coccinelle/api/alloc/pool_zalloc-simple.cocci
Documentation/DMA-API.txt | 7 ++
include/linux/dmapool.h | 6 ++
include/linux/pci.h | 2 +
mm/dmapool.c | 9 ++-
.../coccinelle/api/alloc/pool_zalloc-simple.cocci | 84 ++++++++++++++++++++++
5 files changed, 106 insertions(+), 2 deletions(-)
create mode 100644 scripts/coccinelle/api/alloc/pool_zalloc-simple.cocci
--
1.9.1
next reply other threads:[~2015-07-31 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 19:36 Sean O. Stalley [this message]
2015-07-31 19:36 ` [PATCH v2 1/4] mm: Add support for __GFP_ZERO flag to dma_pool_alloc() Sean O. Stalley
2015-08-12 23:52 ` David Rientjes
2015-07-31 19:36 ` [PATCH v2 2/4] mm: Add dma_pool_zalloc() call to DMA API Sean O. Stalley
2015-07-31 19:36 ` [PATCH v2 3/4] pci: mm: Add pci_pool_zalloc() call Sean O. Stalley
2015-07-31 19:36 ` [PATCH v2 4/4] coccinelle: mm: scripts/coccinelle/api/alloc/pool_zalloc-simple.cocci Sean O. Stalley
2015-08-02 19:30 ` Julia Lawall
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=1438371404-3219-1-git-send-email-sean.stalley@intel.com \
--to=sean.stalley@intel.com \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=bigeasy@linutronix.de \
--cc=cocci@systeme.lip6.fr \
--cc=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=nicolas.palix@imag.fr \
--cc=vinod.koul@intel.com \
/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).