lkml.org 
[lkml]   [2000]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Installing kernel 2.4
On Wed, Nov 08, 2000 at 03:25:56AM +0000, davej@suse.de wrote:
> On Tue, 7 Nov 2000, Jeff V. Merkey wrote:
>
> > If the compiler always aligned all functions and data on 16 byte
> > boundries (NetWare) for all i386 code, it would run a lot faster.
>
> Except on architectures where 16 byte alignment isn't optimal.
>
> > Cache line alignment could be an option in the loader .... after all,
> > it's hte loader that locates data in memory. If Linux were PE based,
> > relocation logic would be a snap with this model (like NT).
>
> Are you suggesting multiple files of differing alignments packed into
> a single kernel image, and have the loader select the correct one at
> runtime ? I really hope I've misinterpreted your intention.

Or more practically, a smart loader than could select a kernel image
based on arch and auto-detect to load the correct image. I don't really
think it matters much what mechanism is used.

What makes more sense is to pack multiple segments for different
processor architecures into a single executable package, and have the
loader pick the right one (the NT model). It could be used for
SMP and non-SMP images, though, as well as i386, i586, i686, etc.

Jeff

>
> regards,
>
> Davej.
>
> --
> | Dave Jones <davej@suse.de> http://www.suse.de/~davej
> | SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

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