From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Cc: Qian Cai <cai-0UDz38MK/Mo@public.gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
yisen.zhuang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
hch-jcswGhMUV9g@public.gmane.org
Subject: Re: [PATCH] dma-debug: Kconfig for PREALLOC_DMA_DEBUG_ENTRIES
Date: Sat, 1 Dec 2018 17:36:57 +0100 [thread overview]
Message-ID: <20181201163657.GA19557@lst.de> (raw)
In-Reply-To: <b22d2ad6-2638-96d7-1df2-24701589202f-5wv7dgnIgG8@public.gmane.org>
On Fri, Nov 30, 2018 at 07:39:50PM +0000, Robin Murphy wrote:
> I was assuming the point was to also add something like
>
> default 131072 if HNS_ENET
>
> so that DMA debug doesn't require too much thought from the user. If they
> still have to notice the overflow message and empirically figure out a
> value that does work, rebuilding the kernel each time is far less
> convenient than simply adding "dma_debug_entries=..." to their kernel
> command line and rebooting, which they can do today. If they do already
> know up-front that the default will need overriding and what the
> appropriate value is, then the command line still seems seems just as
> convenient.
I'm not so fond of random drivers changing the defaults. My idea
was rather to have the config option so that the defconfig files for
the Hisilicon SOCs with this hardware could select a larger number
without making a total mess of the kernel configuration.
If we really have to we could do different defaults, but I'd still
much rather do this on a arch/platform basis than specific drivers.
next prev parent reply other threads:[~2018-12-01 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 17:54 [PATCH] dma-debug: Kconfig for PREALLOC_DMA_DEBUG_ENTRIES Qian Cai
2018-11-30 19:39 ` Robin Murphy
[not found] ` <b22d2ad6-2638-96d7-1df2-24701589202f-5wv7dgnIgG8@public.gmane.org>
2018-12-01 16:36 ` Christoph Hellwig [this message]
[not found] ` <20181201163657.GA19557-jcswGhMUV9g@public.gmane.org>
2018-12-03 11:56 ` John Garry
2018-12-03 17:33 ` 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=20181201163657.GA19557@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=cai-0UDz38MK/Mo@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robin.murphy-5wv7dgnIgG8@public.gmane.org \
--cc=yisen.zhuang-hv44wF8Li93QT0dZR+AlfA@public.gmane.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).