From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Subject: Re: [PATCH 3/5] genetlink: statically initialize families
Date: Mon, 24 Oct 2016 14:55:33 +0200 [thread overview]
Message-ID: <1477313733.4085.11.camel@sipsolutions.net> (raw)
In-Reply-To: <1477312805-7110-4-git-send-email-johannes@sipsolutions.net> (sfid-20161024_144032_073312_7524B853)
On Mon, 2016-10-24 at 14:40 +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Instead of providing macros/inline functions to initialize
> the families, make all users initialize them statically and
> get rid of the macros.
>
> This reduces the kernel code size by about 1.6k on x86-64
> (with allyesconfig).
Actually, with the new system where it's not const, I could even split
this up and submit per subsystem, i.e. the fourth patch doesn't depend
on it. I thought it would, since I wanted to make it const, but since I
failed it doesn't actually have that dependency.
johannes
next prev parent reply other threads:[~2016-10-24 12:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 12:40 [PATCH 0/5] genetlink improvements Johannes Berg
2016-10-24 12:40 ` [PATCH 1/5] genetlink: introduce and use genl_family_attrbuf() Johannes Berg
2016-10-24 12:40 ` [PATCH 2/5] genetlink: no longer support using static family IDs Johannes Berg
2016-10-24 12:40 ` [PATCH 3/5] genetlink: statically initialize families Johannes Berg
2016-10-24 12:55 ` Johannes Berg [this message]
2016-10-25 11:25 ` David Laight
2016-10-25 11:38 ` Johannes Berg
2016-10-24 12:40 ` [PATCH 4/5] genetlink: use idr to track families Johannes Berg
2016-10-24 12:40 ` [PATCH 5/5] genetlink: mark families as __ro_after_init Johannes Berg
2016-10-27 20:16 ` [PATCH 0/5] genetlink improvements David Miller
2016-11-01 17:28 ` new kmemleak reports (was: Re: [PATCH 0/5] genetlink improvements) Jakub Kicinski
2016-11-01 18:32 ` Cong Wang
2016-11-01 18:56 ` Jakub Kicinski
2016-11-02 20:30 ` Cong Wang
2016-11-02 23:47 ` [RFC] make kmemleak scan __ro_after_init section " Jakub Kicinski
2016-11-03 5:40 ` Cong Wang
2016-11-03 15:48 ` Johannes Berg
2016-11-03 20:49 ` Catalin Marinas
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=1477313733.4085.11.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.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).