From: Arend van Spriel <arend@broadcom.com>
To: Denys Vlasenko <dvlasenk@redhat.com>,
Franky Lin <frankyl@broadcom.com>,
Hante Meuleman <meuleman@broadcom.com>,
"John W. Linville" <linville@tuxdriver.com>,
<linux-kernel@vger.kernel.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/4] brcm80211: deinline brcmf_chip_cr4_enterdl, save 440 bytes
Date: Mon, 31 Mar 2014 09:38:49 +0200 [thread overview]
Message-ID: <53391B89.7010304@broadcom.com> (raw)
In-Reply-To: <1396215079-7541-1-git-send-email-dvlasenk@redhat.com>
On 30/03/14 23:31, Denys Vlasenko wrote:
> Automated script discovered that without forced inlining,
> gcc-4.7 generates smaller code for this function.
>
> There is no need to declare static functions inline anyway:
> nowadays gcc detects single-callsite static functions
> which benefit from inlining.
These patches look awfully familiar. I tend to object, but I don't know
the details of this automated script. Does it only look for code size.
How about execution time or is this only compile tested? The other thing
is that you seem to rely on a specific gcc version. What about pre-4.7?
How about different architectures. Was this determined on x86, arm,
sparc, mips. All these questions make me say 'nay'.
Regards,
Arend
> Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
> ---
> drivers/net/wireless/brcm80211/brcmfmac/chip.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/brcm80211/brcmfmac/chip.c b/drivers/net/wireless/brcm80211/brcmfmac/chip.c
> index df130ef..d020b0b 100644
> --- a/drivers/net/wireless/brcm80211/brcmfmac/chip.c
> +++ b/drivers/net/wireless/brcm80211/brcmfmac/chip.c
> @@ -933,7 +933,7 @@ static bool brcmf_chip_cm3_exitdl(struct brcmf_chip_priv *chip)
> return true;
> }
>
> -static inline void
> +static void
> brcmf_chip_cr4_enterdl(struct brcmf_chip_priv *chip)
> {
> struct brcmf_core *core;
>
next prev parent reply other threads:[~2014-03-31 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 21:31 [PATCH 1/4] brcm80211: deinline brcmf_chip_cr4_enterdl, save 440 bytes Denys Vlasenko
2014-03-30 21:31 ` [PATCH 2/4] brcm80211: deinline dma64_dd_upd, save 157 bytes Denys Vlasenko
2014-03-30 21:31 ` [PATCH 3/4] brcm80211: deinline wlc_intstatus, save 429 bytes Denys Vlasenko
2014-03-30 21:31 ` [PATCH 4/4] brcm80211: deinline brcmf_sdio_clrintr, save 8979 bytes Denys Vlasenko
2014-03-31 7:38 ` Arend van Spriel [this message]
2014-03-31 11:18 ` [PATCH 1/4] brcm80211: deinline brcmf_chip_cr4_enterdl, save 440 bytes Denys Vlasenko
2014-03-31 11:19 ` Denys Vlasenko
2014-03-31 13:42 ` Arend van Spriel
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=53391B89.7010304@broadcom.com \
--to=arend@broadcom.com \
--cc=dvlasenk@redhat.com \
--cc=frankyl@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=meuleman@broadcom.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;
as well as URLs for NNTP newsgroup(s).