Messages in this thread | | | From | , "Marchand <@localhost.localdomain Lieven Marchand" <> | Date | Fri, 19 Mar 1999 23:13:36 +0100 (CET) | Subject | Re: Ideas for abstracting driver IO from bus implementation? |
| |
Alan Cox writes: > > supposed to be, anyway? Based on this discussion, it sounds like I2O is > > not much more than asymmetric multiprocessing, where you've got special > > I2O processors sitting in various places (maybe on your motherboard, > > maybe on IO boards, maybe some combination) that just run driver code. > > Hasn't this concept been tried and abandoned enough times before? > > Yes and no. IBM build supercomputers around it. I2O is also very well > designed (much to my initial suprise). The I/O read and write paths of > the block API are a matter of a couple of hundred instructions, the > controller does all the housekeeping work. It creates very low CPU > loads under high I/O loads. So for some server tasks its tailor made. You > can chain a terabyte of raid storage off your system without spending all > your CPU executing scsi code. > > Alan >
How does it compare to IBM's channels and their channel programming facilities? Is there any provision for virtualizing the whole setup like VM had?
Lieven
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |