From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Pekka J Enberg <penberg@cs.Helsinki.FI>
Cc: "Arjan van de Ven" <arjan@infradead.org>,
"Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"Hua Zhong" <hzhong@gmail.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] likely cleanup: remove unlikely for kfree(NULL)
Date: Wed, 26 Apr 2006 21:05:18 +1000 [thread overview]
Message-ID: <444F53EE.7030802@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58.0604261354310.9797@sbz-30.cs.Helsinki.FI>
Pekka J Enberg wrote:
> On Wed, 26 Apr 2006, Arjan van de Ven wrote:
>
>>if you deref'd the pointer it'll optimize it away (assuming a new enough
>>gcc, like 4.1)
>
>
> Here are the numbers for allyesconfig on my setup.
25k out of 25,000k isn't _too_ bad.
On my kernel that should be less than 5k (unless drivers/fses
have a very different ratio of size change versus core code).
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
prev parent reply other threads:[~2006-04-26 17:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 18:21 [PATCH] likely cleanup: remove unlikely for kfree(NULL) Hua Zhong
2006-04-26 7:30 ` Pekka Enberg
2006-04-26 7:53 ` Andreas Mohr
2006-04-26 7:58 ` Arjan van de Ven
2006-04-26 8:16 ` Pekka J Enberg
2006-04-26 8:27 ` Arjan van de Ven
2006-04-26 10:05 ` Adrian Bunk
2006-04-26 10:05 ` Jörn Engel
2006-04-26 10:08 ` Arjan van de Ven
2006-04-26 10:57 ` Pekka J Enberg
2006-04-26 11:03 ` Arjan van de Ven
2006-04-26 11:06 ` Jörn Engel
2006-04-26 11:37 ` Bart Hartgers
2006-04-26 13:04 ` Bart Hartgers
2006-04-26 19:07 ` Kyle Moffett
2006-04-27 6:28 ` Pekka J Enberg
2006-04-27 6:37 ` Nick Piggin
2006-04-27 8:17 ` Bart Hartgers
2006-04-27 15:23 ` Kyle Moffett
2006-04-26 14:11 ` Pekka J Enberg
2006-04-27 5:54 ` Pekka J Enberg
2006-04-27 6:17 ` Nick Piggin
2006-04-27 6:28 ` Pekka J Enberg
2006-04-27 6:50 ` Arjan van de Ven
2006-04-27 8:31 ` Adrian Bunk
2006-04-27 8:41 ` Arjan van de Ven
2006-04-27 8:56 ` Adrian Bunk
2006-04-27 9:08 ` Arjan van de Ven
2006-04-27 11:41 ` Bart Hartgers
2006-04-27 18:23 ` Adrian Bunk
2006-04-27 18:29 ` Arjan van de Ven
2006-04-26 11:05 ` Nick Piggin [this message]
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=444F53EE.7030802@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=hzhong@gmail.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.Helsinki.FI \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.