Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

comp.arch.storage FAQ 2/2
Section - [8.4] HIPPI {Brief}

( Part1 - Part2 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Counties ]


Top Document: comp.arch.storage FAQ 2/2
Previous Document: [8.3] IPI {None}
Next Document: [8.4.1] HIPPI-6400 {Brief}
See reader questions & answers on this topic! - Help others by sharing your knowledge
From: (Device) Interfaces

32-bit transfers at 25 MT/sec., 100 MB/sec. High Performance Parallel
Interface is a unidirectional channel, i.e. you have to have an OUT
cable and and IN cable for bidirectional transfers (you could have
just one, if it's a read-only device like a scanner or write-only like
a frame buffer). HiPPI is not a shared bus, but its frames can be
switched through a crossbar switch (Network Systems is the premiere
vendor).

HiPPI is used for supercomputer-to-supercomputer networking (TCP/IP,
no less), for RAID arrays (from Maximum Strategy, IBM and others),
tape drives (Sony ID-1 drive), frame buffers and increasingly
workstations (SGI and IBM support HiPPI, and 3rd-party Sbus cards
exist for Sun).

Due partly to the high overhead of HiPPI connections, many devices
have elected to separate the control path from the data path. A common
control path in that case is ethernet.

Good resources from the HiPPI Networking Forum on the web at
http://www.esscom.com/hnf/.

User Contributions:

Comment about this article, ask questions, or add new information about this topic:

CAPTCHA




Top Document: comp.arch.storage FAQ 2/2
Previous Document: [8.3] IPI {None}
Next Document: [8.4.1] HIPPI-6400 {Brief}

Part1 - Part2 - Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
rdv@alumni.caltech.edu (Rodney D. Van Meter)





Last Update March 27 2014 @ 02:11 PM