From: Eric Dumazet <dada1@cosmosbay.com>
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 1/3] Uninline the __inet_hash function
Date: Wed, 19 Dec 2007 17:09:21 +0100 [thread overview]
Message-ID: <47694231.2070406@cosmosbay.com> (raw)
In-Reply-To: <47691B0B.2060508@openvz.org>
Pavel Emelyanov a écrit :
> Eric Dumazet wrote:
>> Pavel Emelyanov a écrit :
>>> This one is used in quite many places in the networking code and
>>> seems to big to be inline.
>>>
>>> After the patch net/ipv4/build-in.o loses 725 bytes:
>>> add/remove: 1/0 grow/shrink: 0/5 up/down: 374/-1099 (-725)
>>> function old new delta
>>> __inet_hash - 374 +374
>>> tcp_sacktag_write_queue 2255 2254 -1
>>> __inet_lookup_listener 284 274 -10
>>> tcp_v4_syn_recv_sock 755 495 -260
>>> tcp_v4_hash 389 40 -349
>>> inet_hash_connect 1165 686 -479
>>>
>>> Exporting this is for dccp module.
>>>
>>> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
>>>
>>> ---
>>>
>>> include/net/inet_hashtables.h | 27 ++-------------------------
>>> net/ipv4/inet_hashtables.c | 27 +++++++++++++++++++++++++++
>>> 2 files changed, 29 insertions(+), 25 deletions(-)
>>>
>>> diff --git a/include/net/inet_hashtables.h b/include/net/inet_hashtables.h
>>> index 37f6cb1..1a43125 100644
>>> --- a/include/net/inet_hashtables.h
>>> +++ b/include/net/inet_hashtables.h
>>> @@ -264,31 +264,8 @@ static inline void inet_listen_unlock(struct inet_hashinfo *hashinfo)
>>> wake_up(&hashinfo->lhash_wait);
>>> }
>>>
>>> -static inline void __inet_hash(struct inet_hashinfo *hashinfo,
>>> - struct sock *sk, const int listen_possible)
>>> -{
>>> - struct hlist_head *list;
>>> - rwlock_t *lock;
>>> -
>>> - BUG_TRAP(sk_unhashed(sk));
>>> - if (listen_possible && sk->sk_state == TCP_LISTEN) {
>>> - list = &hashinfo->listening_hash[inet_sk_listen_hashfn(sk)];
>>> - lock = &hashinfo->lhash_lock;
>>> - inet_listen_wlock(hashinfo);
>>> - } else {
>>> - struct inet_ehash_bucket *head;
>>> - sk->sk_hash = inet_sk_ehashfn(sk);
>>> - head = inet_ehash_bucket(hashinfo, sk->sk_hash);
>>> - list = &head->chain;
>>> - lock = inet_ehash_lockp(hashinfo, sk->sk_hash);
>>> - write_lock(lock);
>>> - }
>>> - __sk_add_node(sk, list);
>>> - sock_prot_inc_use(sk->sk_prot);
>>> - write_unlock(lock);
>>> - if (listen_possible && sk->sk_state == TCP_LISTEN)
>>> - wake_up(&hashinfo->lhash_wait);
>>> -}
>>> +extern void __inet_hash(struct inet_hashinfo *hashinfo, struct sock *sk,
>>> + const int listen_possible);
>>>
>>> static inline void inet_hash(struct inet_hashinfo *hashinfo, struct sock *sk)
>>> {
>>> diff --git a/net/ipv4/inet_hashtables.c b/net/ipv4/inet_hashtables.c
>>> index 67704da..46f899b 100644
>>> --- a/net/ipv4/inet_hashtables.c
>>> +++ b/net/ipv4/inet_hashtables.c
>>> @@ -267,6 +267,33 @@ static inline u32 inet_sk_port_offset(const struct sock *sk)
>>> inet->dport);
>>> }
>>>
>>> +void __inet_hash(struct inet_hashinfo *hashinfo, struct sock *sk,
>>> + const int listen_possible)
>>> +{
>>> + struct hlist_head *list;
>>> + rwlock_t *lock;
>>> +
>>> + BUG_TRAP(sk_unhashed(sk));
>>> + if (listen_possible && sk->sk_state == TCP_LISTEN) {
>>> + list = &hashinfo->listening_hash[inet_sk_listen_hashfn(sk)];
>>> + lock = &hashinfo->lhash_lock;
>>> + inet_listen_wlock(hashinfo);
>>> + } else {
>>> + struct inet_ehash_bucket *head;
>>> + sk->sk_hash = inet_sk_ehashfn(sk);
>>> + head = inet_ehash_bucket(hashinfo, sk->sk_hash);
>>> + list = &head->chain;
>>> + lock = inet_ehash_lockp(hashinfo, sk->sk_hash);
>>> + write_lock(lock);
>>> + }
>>> + __sk_add_node(sk, list);
>>> + sock_prot_inc_use(sk->sk_prot);
>>> + write_unlock(lock);
>>> + if (listen_possible && sk->sk_state == TCP_LISTEN)
>>> + wake_up(&hashinfo->lhash_wait);
>>> +}
>>> +EXPORT_SYMBOL_GPL(__inet_hash);
>>> +
>>> /*
>>> * Bind a port for a connect operation and hash it.
>>> */
>> If you un-inline this (good idea), I am not sure we still need listen_possible
>> argument.
>>
>> It was usefull only to help compiler to zap dead code (since it was known at
>> compile time), now it only adds some extra test and argument passing.
>
> Hm... I've tried to address this issue and got worse result - minus
> 600 bytes (vs minus 725). So, what would be more preferable - get a
> smaller code with one extra 'if' or get a bit larger code without it?
>
Strange... What I meant is always assume listen_possible is true.
The if (sk->sk_state == TCP_LISTEN) will finally see the truth.
I did a test here on x86 gcc-4.2.2 and saved 32 bytes.
next prev parent reply other threads:[~2007-12-19 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 10:50 [PATCH net-2.6.25 1/3] Uninline the __inet_hash function Pavel Emelyanov
2007-12-19 12:21 ` Eric Dumazet
2007-12-19 13:22 ` Pavel Emelyanov
2007-12-19 16:09 ` Eric Dumazet [this message]
2007-12-19 17:06 ` Pavel Emelyanov
2007-12-19 17:15 ` Eric Dumazet
2007-12-20 8:30 ` David Miller
2007-12-20 9:46 ` [PATCH net-2.6.25 (resend) " Pavel Emelyanov
2007-12-20 23:31 ` 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=47694231.2070406@cosmosbay.com \
--to=dada1@cosmosbay.com \
--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).