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 18:15:20 +0100 [thread overview]
Message-ID: <476951A8.4040200@cosmosbay.com> (raw)
In-Reply-To: <47694F96.6030604@openvz.org>
Pavel Emelyanov a écrit :
> Eric Dumazet wrote:
>> Pavel Emelyanov a écrit :
>>> Eric Dumazet wrote:
>>>> 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.
>
> That's not truth, if I get you right. The __inet_hash() is called
> with 0, from all the places except for the inet_hash() one.
OK, but on cases with 0, sk->sk_state is != TCP_LISTEN, unless I am mistaken.
>
>> 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.
>>
>>
>>
>
> Thanks,
> Pavel
>
>
next prev parent reply other threads:[~2007-12-19 17:15 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
2007-12-19 17:06 ` Pavel Emelyanov
2007-12-19 17:15 ` Eric Dumazet [this message]
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=476951A8.4040200@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).