RE: Re: Re: DSDT in initrd

From: Pavel Machek [mailto:pavel-+ZI9xUNit7I@public.gmane.org] 

quoted

quoted

quoted

What this enables is not only an elimination of the hassle 

of initrd, it

quoted

enables previously unmodularizable things like ACPI, or 

PCI, or all the

quoted

special code needed for x86 subarchs, or whatever other 

code that one

subarchs are different issue. They can't
be modularized without runtime overhead.

How much runtime overhead?

Hard to tell... It might be 10% in heavy-interrupt-load situation...

Can you help me understand more about why this might be? Why would
modularized code be a performance hit over statically linked? I was
assuming there would be another pointer dereference perhaps but that
certainly is not going to be noticed. We already have drivers in
modules, I'm trying to understand how for example a hi-perf nic driver
performs the same when modularized but subarch stuff wouldn't, when I'm
assuming it would just be like a "driver" for the particular
peculiarities of the platform.

Thanks -- Regards -- Andy


-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5