From: Ingo Oeser <netdev@axxeo.de>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
devel@openvz.org
Subject: Re: [PATCH net-2.6.25 3/3] Uninline the inet_twsk_put function
Date: Thu, 20 Dec 2007 19:32:45 +0100 [thread overview]
Message-ID: <200712201932.45900.netdev@axxeo.de> (raw)
In-Reply-To: <4768F8CD.2050209@openvz.org>
Pavel Emelyanov schrieb:
> This one is not that big, but is widely used: saves 1200 bytes
> from net/ipv4/built-in.o
> +void inet_twsk_put(struct inet_timewait_sock *tw)
> +{
> + if (atomic_dec_and_test(&tw->tw_refcnt)) {
> + struct module *owner = tw->tw_prot->owner;
> + twsk_destructor((struct sock *)tw);
> +#ifdef SOCK_REFCNT_DEBUG
> + printk(KERN_DEBUG "%s timewait_sock %p released\n",
> + tw->tw_prot->name, tw);
> +#endif
> + kmem_cache_free(tw->tw_prot->twsk_prot->twsk_slab, tw);
> + module_put(owner);
> + }
> +}
> +EXPORT_SYMBOL_GPL(inet_twsk_put);
More correct fix seems to be conversion to kref.
Just create out of line inet_twsk_release() containing
sth. similiar to the code inside these braces and modify
inet_twsk_put() to sth. like this:
static inline inet_twsk_put(struct inet_timewait_sock *tw)
{
kref_put(&tw->kref, inet_twsk_release);
}
David, can you see any reason (e.g. some crazy lock stuff) NOT to do this?
Best Regards
Ingo Oeser
next prev parent reply other threads:[~2007-12-20 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 10:56 [PATCH net-2.6.25 3/3] Uninline the inet_twsk_put function Pavel Emelyanov
2007-12-20 18:32 ` Ingo Oeser [this message]
2007-12-21 0:08 ` David Miller
2007-12-21 17:53 ` Ingo Oeser
2007-12-20 23:33 ` 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=200712201932.45900.netdev@axxeo.de \
--to=netdev@axxeo.de \
--cc=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.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).