From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Robin Murphy <robin.murphy@arm.com>, hch@lst.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma-mapping: Reduce dma_mapping_error() inline bloat
Date: Tue, 01 Aug 2017 09:58:07 +0200 [thread overview]
Message-ID: <200b5187-e162-2bc3-7c04-268ae4fcbd61@samsung.com> (raw)
In-Reply-To: <6a23eacf6603e75e995f8720c24b54c4fc2926f5.1500917215.git.robin.murphy@arm.com>
Hi Robin,
On 2017-07-24 19:29, Robin Murphy wrote:
> Thanks to the nested inlining, all drivers correctly calling
> dma_mapping_error() after a mapping a page or single buffer generate two
> calls to get_arch_dma_ops() per callsite, which all adds up to a fair
> old chunk of useless code, e.g. ~3KB for an arm64 defconfig plus extras:
>
> text data bss dec hex filename
> 13051391 1503898 327768 14883057 e318f1 vmlinux.o.old
> 13050751 1503898 327768 14882417 e31671 vmlinux.o.new
>
> Give the compiler a hand by making it clear we want the same ops.
Reviewed-by: Marek Szyprowski <m.szyprowski@samsung.com>
Similar pattern is used in drivers/xen/swiotlb-xen.c for mmap and
get_sgtable. This could be also fixed, although those are not used so
frequently as dma_mapping_error.
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
> include/linux/dma-mapping.h | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/dma-mapping.h b/include/linux/dma-mapping.h
> index 843ab866e0f4..239e53d12ee8 100644
> --- a/include/linux/dma-mapping.h
> +++ b/include/linux/dma-mapping.h
> @@ -541,10 +541,11 @@ static inline void dma_free_noncoherent(struct device *dev, size_t size,
>
> static inline int dma_mapping_error(struct device *dev, dma_addr_t dma_addr)
> {
> - debug_dma_mapping_error(dev, dma_addr);
> + const struct dma_map_ops *ops = get_dma_ops(dev);
>
> - if (get_dma_ops(dev)->mapping_error)
> - return get_dma_ops(dev)->mapping_error(dev, dma_addr);
> + debug_dma_mapping_error(dev, dma_addr);
> + if (ops->mapping_error)
> + return ops->mapping_error(dev, dma_addr);
> return 0;
> }
>
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2017-08-01 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170724172940epcas4p4b06b8fd5c66a475e1f8be1361981a14b@epcas4p4.samsung.com>
2017-07-24 17:29 ` Robin Murphy
2017-08-01 7:58 ` Marek Szyprowski [this message]
2017-08-25 14:56 ` 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=200b5187-e162-2bc3-7c04-268ae4fcbd61@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.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®