From: Andi Kleen <ak@muc.de>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] __initdata strings
Date: Sun, 10 Oct 2004 17:45:12 +0200 [thread overview]
Message-ID: <m38yae1ss7.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <2NNXM-1fZ-5@gated-at.bofh.it> (Oleg Nesterov's message of "Sun, 10 Oct 2004 17:40:07 +0200")
Oleg Nesterov <oleg@tv-sign.ru> writes:
> Hello.
>
> This patch is not intended for inclusion, just for illustration.
>
> __init functions leaves strings (mainly printk's arguments) in
> .data section. It make sense to move them in .init.data.
>
> Is there anyone else who would consider this useful?
There is a more generic way to do this with gcc extensions. Something like
(uncompiled/untested)
#define __i(x) ({ static char __str[] __initdata = x; __str; })
But I'm not sure the few bytes saved are worth the code uglification.
Probably not. likely/unlikely is already bad enough.
-Andi
next parent reply other threads:[~2004-10-10 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2NNXM-1fZ-5@gated-at.bofh.it>
2004-10-10 15:45 ` Andi Kleen [this message]
2004-10-10 16:12 ` [RFC] __initdata strings Oleg Nesterov
2004-10-10 16:36 ` Arnaldo Carvalho de Melo
2004-10-10 15:28 Oleg Nesterov
2004-10-10 16:31 ` Matt Mackall
2004-10-10 16:40 ` Arnaldo Carvalho de Melo
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=m38yae1ss7.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
/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