From: Andrew Morton <akpm@linux-foundation.org>
To: Yury <yury.norov@gmail.com>
Cc: Cassidy Burden <cburden@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Alexey Klimov <klimov.linux@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Daniel Borkmann <dborkman@redhat.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Mark Salter <msalter@redhat.com>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Thomas Graf <tgraf@suug.ch>,
Valentin Rothberg <valentinrothberg@gmail.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [PATCH] lib: Make _find_next_bit helper function inline
Date: Tue, 28 Jul 2015 14:45:37 -0700 [thread overview]
Message-ID: <20150728144537.67d46b5714c99d25f0bb33fb@linux-foundation.org> (raw)
In-Reply-To: <55B7F2C6.9010000@gmail.com>
On Wed, 29 Jul 2015 00:23:18 +0300 Yury <yury.norov@gmail.com> wrote:
> But I think, before/after for x86 is needed as well.
That would be nice.
> And why don't you consider '__always_inline__'? Simple inline is only a
> hint and
> guarantees nothing.
Yup. My x86_64 compiler just ignores the "inline". When I use
__always_inline, find_bit.o's text goes from 776 bytes to 863.
Hopefully we get something in return for that bloat!
Also, if _find_next_bit() benefits from this then _find_next_bit_le()
will presumably also benefit.
next prev parent reply other threads:[~2015-07-28 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 19:09 [PATCH] lib: Make _find_next_bit helper function inline Cassidy Burden
2015-07-28 21:23 ` Yury
2015-07-28 21:38 ` Yury
2015-07-28 21:45 ` Andrew Morton [this message]
2015-07-29 13:30 ` Alexey Klimov
2015-07-29 20:40 ` Cassidy Burden
2015-08-23 22:53 ` Alexey Klimov
2015-08-29 15:15 ` Yury
2015-08-30 21:47 ` Rasmus Villemoes
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=20150728144537.67d46b5714c99d25f0bb33fb@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cburden@codeaurora.org \
--cc=chris@chris-wilson.co.uk \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=klimov.linux@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msalter@redhat.com \
--cc=takahiro.akashi@linaro.org \
--cc=tgraf@suug.ch \
--cc=valentinrothberg@gmail.com \
--cc=yury.norov@gmail.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