From: Robin Murphy <robin.murphy@arm.com>
To: Christoph Hellwig <hch@lst.de>, Qian Cai <cai@gmx.us>
Cc: m.szyprowski@samsung.com, yisen.zhuang@huawei.com,
salil.mehta@huawei.com, iommu@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma-debug: hns_enet_drv could use more DMA entries
Date: Fri, 30 Nov 2018 12:04:47 +0000 [thread overview]
Message-ID: <19e7ac15-a1dc-33ee-d4be-f3433625e836@arm.com> (raw)
In-Reply-To: <20181130084203.GA19812@lst.de>
On 30/11/2018 08:42, Christoph Hellwig wrote:
> On Thu, Nov 29, 2018 at 10:54:56PM -0500, Qian Cai wrote:
>> /* allow architectures to override this if absolutely required */
>> #ifndef PREALLOC_DMA_DEBUG_ENTRIES
>> +/* amount of DMA mappings on this driver is huge. */
>> +#ifdef HNS_ENET
>> +#define PREALLOC_DMA_DEBUG_ENTRIES (1 << 17)
>> +#else
>> #define PREALLOC_DMA_DEBUG_ENTRIES (1 << 16)
>> #endif
>> +#endif
>
> How would this be defined in a header that leaks into this file?
Apparently it wouldn't, because nothing defines that macro anywhere
anyway. CONFIG_HNS_ENET, on the other hand, would be available by virtue
of autoconf.h which is just about everywhere.
> I think we need to turn PREALLOC_DMA_DEBUG_ENTRIES into a user
> selectable config options, as I really don't want to collect hacks like
> this.
Agreed - we already have per-arch overrides scattered about, so growing
special cases in yet another place just makes even more of a mess.
Rounding all of it up into Kconfig would definitely make sense.
Robin.
prev parent reply other threads:[~2018-11-30 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 3:54 Qian Cai
2018-11-30 8:42 ` Christoph Hellwig
2018-11-30 9:16 ` John Garry
2018-11-30 12:04 ` Robin Murphy [this message]
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=19e7ac15-a1dc-33ee-d4be-f3433625e836@arm.com \
--to=robin.murphy@arm.com \
--cc=cai@gmx.us \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=yisen.zhuang@huawei.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
all inboxes | Powered by JetHome®