lkml.org 
[lkml]   [2001]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: crc32 cleanups
Date
On 13 Oct 2001 12:02:16 +0200, 
Andi Kleen <ak@muc.de> wrote:
>Just use the existing linker features. Link the crc code as an .a library.

Does not work if all the code that uses crc32 is in a module. No
references from the main kernel so crc32 is not included by the linker.

>[Note that __initcall may be a bit tricky here if some other __initcall
>user like an ethernet driver needs crc32 too; there is unfortunately no
>priority mechanism in __initcall to enforce that the crc32 init runs before
>the other initcalls. best would probably just to use a static table to avoid
>this issue]

???! __initcall entries are executed in the order that they are linked
into the kernel. The linkage order is controlled by the order that
Makefiles are processed during kbuild and by line order within each
Makefile. There is definitely a priority order for __initcall code.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:08    [W:0.086 / U:0.676 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site