From: Qian Cai <cai@gmx.us>
To: Robin Murphy <robin.murphy@arm.com>, hch@lst.de
Cc: m.szyprowski@samsung.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, salil.mehta@huawei.com,
john.garry@huawei.com, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [PATCH v3 0/7] dma-debug cleanup and dynamic allocation
Date: Mon, 10 Dec 2018 10:50:18 -0500 [thread overview]
Message-ID: <75cd198e-3a4d-0bb4-1b2b-956c8c4e5f9b@gmx.us> (raw)
In-Reply-To: <cover.1544447601.git.robin.murphy@arm.com>
On 12/10/18 9:00 AM, Robin Murphy wrote:
> Hi all,
>
> Here's some assorted cleanup and improvements to dma-debug which grew
> out of the problem that certain drivers use very large numbers of DMA
> mappings, and knowing when to override "dma_debug_entries=..." and what
> value to override it with can be a less-than-obvious task for users.
>
> The main part is patch #4, wherein we make dma-debug clever enough
> to allocate more entries dynamically if needed, such that the
> preallocation value becomes more of a quality-of-life option than a
> necessity. Patches #5 and #6 do some cruft-removal to allow patch #7
> to make the allocation behaviour more efficient in general.
>
> Patches #1, #2 and #4 are some other cleanup and handy features which
> fell out of the discussion/development.
>
> Robin.
>
>
> Robin Murphy (7):
> dma-debug: Use pr_fmt()
> dma-debug: Expose nr_total_entries in debugfs
> dma-debug: Dynamically expand the dma_debug_entry pool
> dma-debug: Make leak-like behaviour apparent
> x86/dma/amd-gart: Stop resizing dma_debug_entry pool
> dma/debug: Remove dma_debug_resize_entries()
> dma-debug: Batch dma_debug_entry allocation
>
> Documentation/DMA-API.txt | 20 +-
> Documentation/x86/x86_64/boot-options.txt | 5 +-
> arch/x86/kernel/amd_gart_64.c | 23 ---
> include/linux/dma-debug.h | 7 -
> kernel/dma/debug.c | 217 ++++++++++------------
> 5 files changed, 109 insertions(+), 163 deletions(-)
>
Tested-by: Qian Cai <cai@lca.pw>
next prev parent reply other threads:[~2018-12-10 15:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 14:00 Robin Murphy
2018-12-10 14:00 ` [PATCH v3 1/7] dma-debug: Use pr_fmt() Robin Murphy
2018-12-10 14:00 ` [PATCH v3 2/7] dma-debug: Expose nr_total_entries in debugfs Robin Murphy
2018-12-10 14:00 ` [PATCH v3 3/7] dma-debug: Dynamically expand the dma_debug_entry pool Robin Murphy
2018-12-10 14:00 ` [PATCH v3 4/7] dma-debug: Make leak-like behaviour apparent Robin Murphy
2018-12-10 14:00 ` [PATCH v3 5/7] x86/dma/amd-gart: Stop resizing dma_debug_entry pool Robin Murphy
2018-12-10 21:26 ` Thomas Gleixner
2018-12-10 14:00 ` [PATCH v3 6/7] dma/debug: Remove dma_debug_resize_entries() Robin Murphy
2018-12-10 14:00 ` [PATCH v3 7/7] dma-debug: Batch dma_debug_entry allocation Robin Murphy
2018-12-10 15:50 ` Qian Cai [this message]
2018-12-11 13:43 ` [PATCH v3 0/7] dma-debug cleanup and dynamic allocation Christoph Hellwig
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=75cd198e-3a4d-0bb4-1b2b-956c8c4e5f9b@gmx.us \
--to=cai@gmx.us \
--cc=bp@alien8.de \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mingo@redhat.com \
--cc=robin.murphy@arm.com \
--cc=salil.mehta@huawei.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®