<
architecture> /i:-too-oh/ (I2O) A specification which aims to provide an
I/O device driver architecture that is independent of both the specific device being controlled and the host
operating system. The H
ardw
are Device Module (HDM) manages the device and the OS Services Module (OSM) interfaces to the host operating system. The HDM is portable across multiple operating systems, processors and busses. The HDM and OSM communicate via a two layer
message passing protocol. A Message Layer sets up a communications session and runs on top of a Transport Layer which defines how the two p
arties sh
are information. I2O is also designed to facilitate intelligent I/O subsystems, with support for
message passing between multiple independent processors. By relieving the host of
interrupt intensive I/O tasks required by the v
arious layers of a driver
architecture, the I2O intelligent I/O
architecture greatly improves I/O performance. I2O systems will be able to more efficiently deliver the I/O throughput required by a wide range of high bandwidth applications, such as networked
video,
groupware and
client-server processing. I2O does not restrict where the layered modules execute, providing support for single processor,
multiprocessor, and
clustered systems. I2O is not intended to replace the driver
architectures currently in existence. Rather, the objective is to provide an open, stand
ards-based approach, which is complement
ary to existing drivers, and provides a framework for the rapid development of a new generation of portable, intelligent I/O.
Start . (1997-11-04)
In addition suitable contents:
[ 2 ] [ = ] [ ag ] [ ai ] [ al ] [ am ] [ an ] [ app ] [ application ] [ ar ] [ arc ] [ architecture ] [ as ] [ at ] [ B ] [ b ] [ ba ] [ bandwidth ] [ base ] [ be ] [ bj ] [ bo ] [ bot ] [ bs ] [ bus ] [ by ] [ ca ] [ cat ] [ ch ] [ ci ] [ cl ] [ client ] [ client-server ] [ cluster ] [ co ] [ com ] [ complement ] [ con ] [ control ] [ cr ] [ cu ] [ current ] [ D ] [ de ] [ design ] [ development ] [ device ] [ device driver ] [ ding ] [ do ] [ driver ] [ drivers ] [ du ] [ ec ] [ ed ] [ ee ] [ er ] [ era ] [ es ] [ et ] [ exec ] [ execute ] [ fi ] [ file ] [ fo ] [ for ] [ fr ] [ frame ] [ framework ] [ ge ] [ gen ] [ generation ] [ gh ] [ gl ] [ gn ] [ gr ] [ group ] [ h ] [ hat ] [ HD ] [ HDM ] [ hit ] [ host ] [ hr ] [ ht ] [ I2O ] [ id ] [ ie ] [ il ] [ in ] [ int ] [ interface ] [ interrupt ] [ io ] [ I/O ] [ ir ] [ is ] [ it ] [ ke ] [ la ] [ layer ] [ Lex ] [ li ] [ ls ] [ lt ] [ lu ] [ ly ] [ M ] [ ma ] [ man ] [ message ] [ message passing ] [ mm ] [ mo ] [ mod ] [ module ] [ mp ] [ ms ] [ mu ] [ multiprocessor ] [ na ] [ nc ] [ ne ] [ net ] [ network ] [ nf ] [ ng ] [ ni ] [ no ] [ ns ] [ O ] [ object ] [ om ] [ op ] [ open ] [ operating system ] [ org ] [ OS ] [ pa ] [ pe ] [ perf ] [ ph ] [ pl ] [ pm ] [ port ] [ portable ] [ pr ] [ process ] [ processing ] [ processor ] [ protocol ] [ pt ] [ pw ] [ query ] [ range ] [ rc ] [ re ] [ ro ] [ roach ] [ ru ] [ run ] [ S ] [ sa ] [ se ] [ serve ] [ server ] [ session ] [ set ] [ sh ] [ shar ] [ si ] [ sig ] [ sk ] [ so ] [ spec ] [ specification ] [ st ] [ standard ] [ strict ] [ su ] [ support ] [ sy ] [ system ] [ T ] [ table ] [ tar ] [ th ] [ throughput ] [ to ] [ tp ] [ tr ] [ troll ] [ tt ] [ tw ] [ ug ] [ up ] [ us ] [ va ] [ var ] [ ve ] [ vi ] [ ye ]