From: jamal <hadi@cyberus.ca>
To: Denis Vlasenko <vda.linux@googlemail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 800+ byte inlines in include/net/pkt_act.h
Date: Mon, 21 Aug 2006 08:26:00 -0400 [thread overview]
Message-ID: <1156163160.5126.47.camel@jzny2> (raw)
In-Reply-To: <200608201933.10293.vda.linux@googlemail.com>
On Sun, 2006-20-08 at 19:33 +0200, Denis Vlasenko wrote:
> Hi,
>
> include/net/pkt_act.h plays a game of inlines
> which are kind of "templatized", like this:
>
> act_ipt.c:
>
> /* ovewrride the defaults */
> #define tcf_st tcf_ipt
> #define tcf_t_lock ipt_lock
> #define tcf_ht tcf_ipt_ht
> #define CONFIG_NET_ACT_INIT
> #include <net/pkt_act.h>
>
> This results in code duplication. For example,
> tcf_generic_walker() is duplicated four times.
> On i386 it is about 4*800 bytes in text section.
> Other inlines are a bit smaller but still are substantial.
As per last discussion, either Patrick McHardy or myself are going to
work on it - at some point. Please be patient. The other alternative is:
you fix it and send patches.
Note that even after conversion, functions like tcf_generic_walker() are
not going to save much in total .text sizes; also note they run the
control path and are typically not as much invoked and therefore not
performance impacting on smaller cache systems..
cheers,
jamal
next prev parent reply other threads:[~2006-08-21 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 17:33 800+ byte inlines in include/net/pkt_act.h Denis Vlasenko
2006-08-21 12:26 ` jamal [this message]
2006-08-21 23:38 ` David Miller
2006-08-22 13:45 ` jamal
2006-08-22 6:56 ` David Miller
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=1156163160.5126.47.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vda.linux@googlemail.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).