From: Rusty Russell <rusty@rustcorp.com.au>
To: Jan Beulich <JBeulich@novell.com>
Cc: Ingo Molnar <mingo@elte.hu>,
tony.luck@intel.com, Thomas Gleixner <tglx@linutronix.de>,
hpa@zytor.com, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] reduce export symbol CRC table size on 64-bit archs
Date: Wed, 1 Jul 2009 14:30:28 +0930 [thread overview]
Message-ID: <200907011430.29524.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4A4A18780200007800008345@vpn.id2.novell.com>
On Tue, 30 Jun 2009 09:21:52 pm Jan Beulich wrote:
> Since these CRCs are really only 32-bit quantities, there's no need to
> store them in 64-bit slots. Since, however, gcc doesn't allow
> respective initializations, asm() constructs get used to create the CRC
> tables (and its for that reason that the patch only makes x86-64 and
> ia64 utilize that functionality, as I can't verify this doesn't break
> in some subtle way elsewhere).
Hmm, can we change the build system to just link this in as a normal table,
rather than use linker tricks?
Then genksyms would just spit out a C file we could compile and link into final
vmlinux.
Thanks,
Rusty.
next prev parent reply other threads:[~2009-07-01 5:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 11:51 [PATCH] reduce export symbol CRC table size on 64-bit archs Jan Beulich
2009-06-30 11:51 ` Jan Beulich
2009-06-30 22:09 ` Ingo Molnar
2009-07-01 5:00 ` Rusty Russell [this message]
2009-07-01 5:00 ` Rusty Russell
2009-07-01 7:00 ` Jan Beulich
2009-07-01 7:00 ` Jan Beulich
[not found] ` <4A4A18780200007800008345-Qfbpwmsw6RoS3W1tAdPHOtBPR1lH4CV8@public.gmane.org>
2009-07-03 20:16 ` Michal Marek
2009-07-03 20:16 ` Michal Marek
2009-07-06 7:42 ` Jan Beulich
[not found] ` <4A51C71B0200007800008EE2-Qfbpwmsw6RoS3W1tAdPHOtBPR1lH4CV8@public.gmane.org>
2009-07-09 11:14 ` Rusty Russell
2009-07-09 11:14 ` Rusty Russell
2009-07-10 7:23 ` Jan Beulich
[not found] ` <4A57089B0200007800009C0E-Qfbpwmsw6RoS3W1tAdPHOtBPR1lH4CV8@public.gmane.org>
2009-07-10 14:36 ` H. Peter Anvin
2009-07-10 14:36 ` H. Peter Anvin
2009-07-10 15:50 ` Jon Masters
2009-07-10 15:50 ` Jon Masters
2009-07-13 8:11 ` Michal Marek
2009-07-13 8:11 ` Michal Marek
2009-07-13 8:44 ` Jan Beulich
[not found] ` <4A5B101E020000780000A284-Qfbpwmsw6RoS3W1tAdPHOtBPR1lH4CV8@public.gmane.org>
2009-07-14 10:29 ` Jon Masters
2009-07-14 10:29 ` Jon Masters
[not found] ` <1247567372.31188.229.camel-gHXTUq7nJ1kAgR79ElizB2+biTydnCM9ILAQCsJbaHk@public.gmane.org>
2009-07-14 10:44 ` Marco d'Itri
2009-07-14 10:44 ` Marco d'Itri
2009-07-14 16:43 ` H. Peter Anvin
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=200907011430.29524.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=JBeulich@novell.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
/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