[lkml]   [2000]   [Oct]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Proposal: driver initialization pipelining
Thus spake Andre Hedrick (
> > Some of the initialization can definitely be done in parallel, but there
> > are all sorts of special cases, like devices which turn off interrupts
> > during init (IDE), and other fun tricks... Some of the delays during
> > init are timing sensitive, where you don't want to have to wait for the
> > tasklet to be called for completion.
> I will be happy to break the IRQ code for a demo for Felix.
> But do backup your data first, because it will not be there when you boot
> again!

I don't get it.
If you say that IDE disables interrupts during init, does that mean that
it disables _all_ interrupts or just that you mask the IDE IRQs?

Actually, I was thinking more along the lines of SCSI bus scan, because
the Linux IDE reset is already barely noticeable.

Does "timing sensitive" mean "don't come again too early" or "be 100%

There ought to be _some_ initializations that don't require interrupts?
Registering the file systems and network protocols, stuff like that?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

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