From: Robin Murphy <robin.murphy@arm.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Christoph Hellwig <hch@lst.de>, Joerg Roedel <jroedel@suse.de>,
iommu@lists.linux-foundation.org,
Eric Dumazet <eric.dumazet@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dma-debug: dynamic allocation of hash table
Date: Sat, 1 Feb 2020 00:06:12 +0000 [thread overview]
Message-ID: <6ad5e108-1368-bd1e-0be7-eff02eed1e5c@arm.com> (raw)
In-Reply-To: <CANn89iKmFMiOStfcRdKXe=mks65dhkXPTawqevY8YwyUbfSjhg@mail.gmail.com>
On 2020-01-31 5:46 pm, Eric Dumazet wrote:
> On Fri, Jan 31, 2020 at 9:43 AM Robin Murphy <robin.murphy@arm.com> wrote:
>>
>> On 31/01/2020 2:42 pm, Eric Dumazet wrote:
>>> On Fri, Jan 31, 2020 at 4:30 AM Robin Murphy <robin.murphy@arm.com> wrote:
>>>>
>>>> ...and when that represents ~5% of the total system RAM it is a *lot*
>>>> less reasonable than even 12KB. As I said, it's great to make a debug
>>>> option more efficient such that what it observes is more representative
>>>> of the non-debug behaviour, but it mustn't come at the cost of making
>>>> the entire option unworkable for other users.
>>>>
>>>
>>> Then I suggest you send a patch to reduce PREALLOC_DMA_DEBUG_ENTRIES
>>> because having 65536 preallocated entries consume 4 MB of memory.
>>
>> ...unless it's overridden on the command-line ;)
>>
>>> Actually this whole attempt to re-implement slab allocations in this
>>> file is suspect.
>>
>> Again that's a matter of expected usage patterns - typically the
>> "reasonable default" or user-defined preallocation should still be
>> enough (as it *had* to be before), and the kind of systems that can
>> sustain so many live mappings as to regularly hit the dynamic expansion
>> path are also likely to have enough memory not to care that later-unused
>> entries never get 'properly' freed back to the kernel (plus as you've
>> observed, many workloads tend to reach a steady state where entries are
>> mostly only transiently free anyway). The reasoning for the exact
>> implementation details is there in the commit logs.
>>
>>> Do not get me wrong, but if you really want to run linux on a 16MB host,
>>> I guess you need to add CONFIG_BASE_SMALL all over the places,
>>> not only in this kernel/dma/debug.c file.
>>
>> Right, nobody's suggesting that defconfig should "just work" on your
>> router/watch/IoT shoelaces/whatever, I'm just saying that tuning any
>> piece of common code for datacenter behemoths, for quality-of-life
>> rather than functional necessity, and leaving no way to adjust it other
>> than hacking the source, would represent an unnecessary degree of
>> short-sightedness that we can and should avoid.
>>
>> Taking a closer look at the code, it appears fairly straightforward to
>> make the hash size variable, and in fact making it self-adjusting
>> doesn't seem too big a jump from there. I'm happy to have a go at that
>> myself if you like.
>
>
> Sure, go ahead, I have no plan implementing changes for 20 years old platforms.
Heh, I'm fairly confident the 20-year-old drivers are probably
well-debugged by now anyway - it's the future low-end SoCs for
Linux-powered IoT shoelaces that I see being a rich vein of new bugs :)
How does this look to start with? (only compile-tested so far, but I'll
pick it up again properly next week)
Robin.
----->8-----
From: Robin Murphy <robin.murphy@arm.com>
Subject: [PATCH] dma/debug: Size hash table dynamically
Having a fixed-size hash table fails to scale nicely - making it large
enough to perform well for the mapping behaviour of big network adapters
tends towards unreasonable memory consumption for smaller systems. It's
logical to size the table for the number of expected entries, and doing
so conveniently puts the size/performance tradeoff in the hands of the
user via the "dma_debug_entries" option. The dynamic allocation also
sidesteps the issue of the static array bloating the kernel image on
certain platforms.
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
---
kernel/dma/debug.c | 31 ++++++++++++++++++++-----------
1 file changed, 20 insertions(+), 11 deletions(-)
diff --git a/kernel/dma/debug.c b/kernel/dma/debug.c
index 2031ed1ad7fa..86a4c68d6ac1 100644
--- a/kernel/dma/debug.c
+++ b/kernel/dma/debug.c
@@ -27,9 +27,9 @@
#include <asm/sections.h>
-#define HASH_SIZE 16384ULL
+static int hash_size __read_mostly;
#define HASH_FN_SHIFT 13
-#define HASH_FN_MASK (HASH_SIZE - 1)
+#define HASH_FN_MASK (hash_size - 1)
#define PREALLOC_DMA_DEBUG_ENTRIES (1 << 16)
/* If the pool runs out, add this many new entries at once */
@@ -90,7 +90,7 @@ struct hash_bucket {
};
/* Hash list to save the allocated dma addresses */
-static struct hash_bucket dma_entry_hash[HASH_SIZE];
+static struct hash_bucket *dma_entry_hash;
/* List of pre-allocated dma_debug_entry's */
static LIST_HEAD(free_entries);
/* Lock for the list above */
@@ -398,7 +398,7 @@ void debug_dma_dump_mappings(struct device *dev)
{
int idx;
- for (idx = 0; idx < HASH_SIZE; idx++) {
+ for (idx = 0; idx < hash_size; idx++) {
struct hash_bucket *bucket = &dma_entry_hash[idx];
struct dma_debug_entry *entry;
unsigned long flags;
@@ -818,7 +818,7 @@ static int dump_show(struct seq_file *seq, void *v)
{
int idx;
- for (idx = 0; idx < HASH_SIZE; idx++) {
+ for (idx = 0; idx < hash_size; idx++) {
struct hash_bucket *bucket = &dma_entry_hash[idx];
struct dma_debug_entry *entry;
unsigned long flags;
@@ -862,7 +862,7 @@ static int device_dma_allocations(struct device
*dev, struct dma_debug_entry **o
unsigned long flags;
int count = 0, i;
- for (i = 0; i < HASH_SIZE; ++i) {
+ for (i = 0; i < hash_size; ++i) {
spin_lock_irqsave(&dma_entry_hash[i].lock, flags);
list_for_each_entry(entry, &dma_entry_hash[i].list, list) {
if (entry->dev == dev) {
@@ -934,7 +934,13 @@ static int dma_debug_init(void)
if (global_disable)
return 0;
- for (i = 0; i < HASH_SIZE; ++i) {
+ hash_size = roundup_pow_of_two(nr_prealloc_entries) / 16;
+ dma_entry_hash = kvmalloc_array(max(hash_size, 16),
+ sizeof(*dma_entry_hash), GFP_KERNEL);
+ if (!dma_entry_hash)
+ goto out_err;
+
+ for (i = 0; i < hash_size; ++i) {
INIT_LIST_HEAD(&dma_entry_hash[i].list);
spin_lock_init(&dma_entry_hash[i].lock);
}
@@ -950,10 +956,7 @@ static int dma_debug_init(void)
pr_warn("%d debug entries requested but only %d allocated\n",
nr_prealloc_entries, nr_total_entries);
} else {
- pr_err("debugging out of memory error - disabled\n");
- global_disable = true;
-
- return 0;
+ goto out_err;
}
min_free_entries = num_free_entries;
@@ -961,6 +964,12 @@ static int dma_debug_init(void)
pr_info("debugging enabled by kernel config\n");
return 0;
+
+out_err:
+ pr_err("debugging out of memory error - disabled\n");
+ global_disable = true;
+
+ return 0;
}
core_initcall(dma_debug_init);
--
2.17.1
next prev parent reply other threads:[~2020-02-01 0:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 19:10 Eric Dumazet
2020-01-30 23:46 ` Robin Murphy
2020-01-31 0:17 ` Eric Dumazet
2020-01-31 12:30 ` Robin Murphy
2020-01-31 14:42 ` Eric Dumazet
2020-01-31 17:43 ` Robin Murphy
2020-01-31 17:46 ` Eric Dumazet
2020-02-01 0:06 ` Robin Murphy [this message]
2020-01-31 9:06 ` Geert Uytterhoeven
2020-01-31 11:33 ` Robin Murphy
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=6ad5e108-1368-bd1e-0be7-eff02eed1e5c@arm.com \
--to=robin.murphy@arm.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.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®