From: Johannes Berg <johannes@sipsolutions.net>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Peter Zijlstra <peterz@infradead.org>,
Jason Baron <jbaron@akamai.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: static key arrays?
Date: Fri, 11 Sep 2015 16:55:08 +0200 [thread overview]
Message-ID: <1441983308.2083.13.camel@sipsolutions.net> (raw)
In-Reply-To: <87zj0taui1.fsf@rasmusvillemoes.dk> (sfid-20150911_164128_138967_59961D8F)
On Fri, 2015-09-11 at 16:41 +0200, Rasmus Villemoes wrote:
>
> That's inconvenient for large arrays. I think the 'or something' would
> be the range initialization supported by gcc (and I think also clang):
>
> struct static_key_false array[N] = { [0 ... N-1] = STATIC_KEY_FALSE_INIT };
>
Ah, I wasn't aware of that extension. That's indeed much more
convenient than the CPP trick I was thinking of :)
johannes
next prev parent reply other threads:[~2015-09-11 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 9:45 static key arrays? Johannes Berg
2015-09-11 11:10 ` Peter Zijlstra
2015-09-11 12:14 ` Johannes Berg
2015-09-11 14:41 ` Rasmus Villemoes
2015-09-11 14:55 ` Johannes Berg [this message]
2015-09-11 11:17 ` Baron, Jason
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=1441983308.2083.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jbaron@akamai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=peterz@infradead.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