Re: [2.4.17/18pre] VM and swap - it's really unusable

[Alan Cox]

> Obvioiusly, Alan, you know more about the networking stack than I do. :)  But 
> could you define "large periods of time running other code"?

10ths of a second if there is a lot to let run instead of this thread. Even
1/100th is bad news. 

> There ISN'T an upper bound on interrupts.  We've got some nasty interrupts in 
> the system.  How long does the PCI bus get tied up with spinning video cards 
> flooding the bus to make their benchmarks look 5% better?  How long of a 

They dont flood the bus with interrupts, the lock the bus off for several
millseconds worst case. Which btw you'll note means that lowlatency already
achieves the best value you can get

> latency spike did we (until recently) get switching between graphics and text 
> consoles?  (I heard that got fixed, moved into a tasklet or some such.  
> Haven't looked at it yet.)  Without Andre's IDE patches, how much latency can 

Been fixed in -ac for ages, and finally made Linus tree.

> the disk insert at random?

IDE with or without Andre's changes can insert multiple millisecond delays
on the bus in some situations. Again pre-empt patch can offer you nothing 
because the hardware limit is easily met by low latency

> One other fun little thing about the scheduler: a process that is submitting 
> network packets probably isn't entirely CPU bound, is it?  It's doing I/O.  

Network packets get submitted from _outside_

Alan