From: Arjan van de Ven <arjan@linux.intel.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: akpm@osdl.org, bunk@stusta.de, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/17] Infrastructure to mark exported symbols as unused-for-removal-soon
Date: Tue, 02 May 2006 18:23:27 +0200 [thread overview]
Message-ID: <4457877F.5000406@linux.intel.com> (raw)
In-Reply-To: <20060502092440.91fe8797.rdunlap@xenotime.net>
Randy.Dunlap wrote:
> On Tue, 02 May 2006 16:53:07 +0200 Arjan van de Ven wrote:
>
>> Hi,
>> As discussed on lkml before; the patch with the infrastructure to deprecate unused symbols
>>
>> This is patch one in a series of 17; to not overload lkml the other 16 will be mailed direct;
>> people who want to see them all can see them at http://www.fenrus.org/unused
>>
>>
>>
>> This patch temporarily adds EXPORT_UNUSED_SYMBOL and EXPORT_UNUSED_SYMBOL_GPL.
>> These will be used as transition measure for symbols that aren't used in the
>> kernel and are on the way out. When a module uses such a symbol, a warning
>> is printk'd at modprobe time.
>>
>> The main reason for removing unused exports is size: eacho export takes roughly
>> between 100 and 150 bytes of kernel space in the binary. This patch gives
>> users the option to immediately get this size gain via a config option.
>
> Do the exports take any space at runtime in RAM?
yes; roughly 100 to 150 bytes or so
> scsi patch comments (only one that I have seen) say:
> +EXPORT_UNUSED_SYMBOL(scsi_print_status); /* removal in 2.6.19 */
>
> and When: above says "before 2.6.19". Those don't agree.
> Please fix. Thanks.
there's no conflict actually; they'll be gone in 2.6.19, by removing them just before that ;)
next prev parent reply other threads:[~2006-05-02 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 14:53 [patch 1/17] Infrastructure to mark exported symbols as unused-for-removal-soon Arjan van de Ven
2006-05-02 16:24 ` Randy.Dunlap
2006-05-02 16:23 ` Arjan van de Ven [this message]
2006-05-09 16:02 ` Andrew Morton
2006-05-09 16:13 ` Arjan van de Ven
2006-05-09 16:27 ` Jörn Engel
2006-05-09 17:23 ` Alan Cox
2006-05-11 6:34 ` Paul Jackson
2006-05-11 7:15 ` Arjan van de Ven
2006-05-11 8:06 ` Paul Jackson
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=4457877F.5000406@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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