From: Tom Lendacky <thomas.lendacky@amd.com>
To: David Rientjes <rientjes@google.com>, Christoph Hellwig <hch@lst.de>
Cc: Brijesh Singh <brijesh.singh@amd.com>,
Jon Grimm <jon.grimm@amd.com>, Joerg Roedel <joro@8bytes.org>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org
Subject: Re: [patch 5/7] dma-pool: add pool sizes to debugfs
Date: Wed, 15 Apr 2020 08:45:08 -0500 [thread overview]
Message-ID: <0c7144e3-057a-959d-0b7d-4a718bd6076c@amd.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2004141704050.68516@chino.kir.corp.google.com>
On 4/14/20 7:04 PM, David Rientjes wrote:
> The atomic DMA pools can dynamically expand based on non-blocking
> allocations that need to use it.
>
> Export the sizes of each of these pools, in bytes, through debugfs for
> measurement.
>
> Suggested-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
> kernel/dma/pool.c | 41 +++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 41 insertions(+)
>
> diff --git a/kernel/dma/pool.c b/kernel/dma/pool.c
> index cf052314d9e4..3e22022c933b 100644
> --- a/kernel/dma/pool.c
> +++ b/kernel/dma/pool.c
> @@ -2,6 +2,7 @@
> /*
> * Copyright (C) 2020 Google LLC
> */
> +#include <linux/debugfs.h>
> #include <linux/dma-direct.h>
> #include <linux/dma-noncoherent.h>
> #include <linux/dma-contiguous.h>
> @@ -15,6 +16,11 @@
> static struct gen_pool *atomic_pool_dma __ro_after_init;
> static struct gen_pool *atomic_pool_dma32 __ro_after_init;
> static struct gen_pool *atomic_pool_kernel __ro_after_init;
> +#ifdef CONFIG_DEBUG_FS
I don't think you need the #ifdef any more unless you just want to save
space. All of the debugfs routines have versions for whether
CONFIG_DEBUG_FS is defined or not.
> +static unsigned long pool_size_dma;
> +static unsigned long pool_size_dma32;
> +static unsigned long pool_size_kernel;
> +#endif
>
> #define DEFAULT_DMA_COHERENT_POOL_SIZE SZ_256K
> static size_t atomic_pool_size = DEFAULT_DMA_COHERENT_POOL_SIZE;
> @@ -29,6 +35,38 @@ static int __init early_coherent_pool(char *p)
> }
> early_param("coherent_pool", early_coherent_pool);
>
> +#ifdef CONFIG_DEBUG_FS
> +static void __init dma_atomic_pool_debugfs_init(void)
> +{
> + struct dentry *root;
> +
> + root = debugfs_create_dir("dma_pools", NULL);
> + if (IS_ERR_OR_NULL(root))
> + return;
I believe GregKH went through and removed a lot of these error checks (see
9e3926df8779 ("xgbe: no need to check return value of debugfs_create
functions") for an example).
Thanks,
Tom
> +
> + debugfs_create_ulong("pool_size_dma", 0400, root, &pool_size_dma);
> + debugfs_create_ulong("pool_size_dma32", 0400, root, &pool_size_dma32);
> + debugfs_create_ulong("pool_size_kernel", 0400, root, &pool_size_kernel);
> +}
> +
> +static void dma_atomic_pool_size_add(gfp_t gfp, size_t size)
> +{
> + if (gfp & __GFP_DMA)
> + pool_size_dma += size;
> + else if (gfp & __GFP_DMA32)
> + pool_size_dma32 += size;
> + else
> + pool_size_kernel += size;
> +}
> +#else
> +static inline void dma_atomic_pool_debugfs_init(void)
> +{
> +}
> +static inline void dma_atomic_pool_size_add(gfp_t gfp, size_t size)
> +{
> +}
> +#endif /* CONFIG_DEBUG_FS */
> +
> static int atomic_pool_expand(struct gen_pool *pool, size_t pool_size,
> gfp_t gfp)
> {
> @@ -76,6 +114,7 @@ static int atomic_pool_expand(struct gen_pool *pool, size_t pool_size,
> if (ret)
> goto encrypt_mapping;
>
> + dma_atomic_pool_size_add(gfp, pool_size);
> return 0;
>
> encrypt_mapping:
> @@ -160,6 +199,8 @@ static int __init dma_atomic_pool_init(void)
> if (!atomic_pool_dma32)
> ret = -ENOMEM;
> }
> +
> + dma_atomic_pool_debugfs_init();
> return ret;
> }
> postcore_initcall(dma_atomic_pool_init);
>
next prev parent reply other threads:[~2020-04-15 13:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 0:04 [patch 0/7] unencrypted atomic DMA pools with dynamic expansion David Rientjes
2020-04-15 0:04 ` [patch 1/7] dma-remap: separate DMA atomic pools from direct remap code David Rientjes
2020-04-17 7:06 ` Christoph Hellwig
2020-04-15 0:04 ` [patch 2/7] dma-pool: add additional coherent pools to map to gfp mask David Rientjes
2020-04-15 0:04 ` [patch 3/7] dma-pool: dynamically expanding atomic pools David Rientjes
2020-04-15 0:04 ` [patch 4/7] dma-direct: atomic allocations must come from atomic coherent pools David Rientjes
2020-04-17 7:09 ` Christoph Hellwig
2020-04-15 0:04 ` [patch 5/7] dma-pool: add pool sizes to debugfs David Rientjes
2020-04-15 13:45 ` Tom Lendacky [this message]
2020-04-17 7:10 ` Christoph Hellwig
2020-04-15 0:05 ` [patch 6/7] x86/mm: unencrypted non-blocking DMA allocations use coherent pools David Rientjes
2020-04-15 0:05 ` [patch 7/7] dma-pool: scale the default DMA coherent pool size with memory capacity David Rientjes
2020-04-17 7:11 ` [patch 0/7] unencrypted atomic DMA pools with dynamic expansion Christoph Hellwig
2020-04-17 18:41 ` David Rientjes
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=0c7144e3-057a-959d-0b7d-4a718bd6076c@amd.com \
--to=thomas.lendacky@amd.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=jon.grimm@amd.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).