Browse Prior Art Database

High Speed Large Data Transfers between PS/2S using SCSI Adapters

IP.com Disclosure Number: IPCOM000108979D
Original Publication Date: 1992-Jul-01
Included in the Prior Art Database: 2005-Mar-23
Document File: 8 page(s) / 288K

Publishing Venue

IBM

Related People

Bade, S: AUTHOR [+2]

Abstract

A protocol for high-speed transferring of data between PS/2*s with SCSI (Small Computer System Architecture) adapters is disclosed. Verbs and control blocks define the interface between the PS/2s and an application program.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 29% of the total text.

High Speed Large Data Transfers between PS/2S using SCSI Adapters

       A protocol for high-speed transferring of data between
PS/2*s with SCSI (Small Computer System Architecture) adapters is
disclosed.  Verbs and control blocks define the interface between the
PS/2s and an application program.

      This article provides a high-speed data transfer protocol
between two PS/2's using SCSI adapters.  The following set of verbs
and control blocks defines the interface between the two PS/2s and
the interface to a generic multiprocessing operation system.

      The SCSI adapters are set up to be both senders of data
(initiator) and receivers of data (target), allowing bidirectional
data transfer.  Each PS/2 provides an interprocess communication
facility.

      When the device driver installs itself, it creates one process
to handle all the requests, a hardware interrupt handler to handle
input from the SCSI adapter, and a timer to allow for hardware
timeouts.  After installing the necessary operating system hooks, the
device driver initializes the SCSI adapter and waits for a request.

      The following messages have been defined to allow
communications between the device driver process providing the
service and the other application processes in the system.

      To communicate errors and state changes back to the application
process, all messages should have a return code field.  Return codes
are used to report errors if the connection to the remote PS/2 should
fail during an operation, report errors in the syntax of the message,
and relay the status of the remote process.
CONNECT:

      This message establishes a logical software connection between
the device driver on the local PS/2 and the remote PS/2.  The
connector passes its name and the name of the process on the remote
PS/2.  The names are saved and a connection ID is passed back to the
connector.  After the connection request all other requests are made
using the connection ID (see Fig. 1).
SEND MESSAGE:

      This allows a process on one PS/2 to send a message to a
connected process on the remote PS/2.  The caller passes the
connection ID and the message to send to the remote process.  The
message is shipped to the remote side and sent to the connected
remote process (see Fig. 2).
GET DATA:

      This allows a process on the requesting PS/2 to get a block of
data from the remote PS/2.  The caller passes the connection ID, the
address of the remote data, the address of its buffer where the data
should be placed, and the data length (see Fig. 3).
PUT DATA:

      This allows a process on the requesting PS/2 to transfer data
to the remote PS/2.  The caller passes the connection ID, the
destination address in the remote PS/2, the local address of the
data, and the data length (see Fig. 4).
PUT DATA WITH RC:

      This allows a process on the requesting PS/2 to transfer data
to the remote PS/2 and cause the process on the...