CA2704138A1 - Providing indirect data addressing in an input/output processing system where the indirect data address list is non-contiguous - Google Patents
Providing indirect data addressing in an input/output processing system where the indirect data address list is non-contiguous Download PDFInfo
- Publication number
- CA2704138A1 CA2704138A1 CA2704138A CA2704138A CA2704138A1 CA 2704138 A1 CA2704138 A1 CA 2704138A1 CA 2704138 A CA2704138 A CA 2704138A CA 2704138 A CA2704138 A CA 2704138A CA 2704138 A1 CA2704138 A1 CA 2704138A1
- Authority
- CA
- Canada
- Prior art keywords
- data
- list
- channel
- address
- storage
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/10—Address translation
- G06F12/1027—Address translation using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB]
- G06F12/1036—Address translation using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB] for multiple virtual address spaces, e.g. segmentation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/10—Program control for peripheral devices
- G06F13/12—Program control for peripheral devices using hardware independent of the central processor, e.g. channel or peripheral processor
- G06F13/124—Program control for peripheral devices using hardware independent of the central processor, e.g. channel or peripheral processor where hardware is a sequential transfer control unit, e.g. microprocessor, peripheral processor or state-machine
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/10—Address translation
- G06F12/1009—Address translation using page tables, e.g. page table structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/65—Details of virtual memory and virtual address translation
Abstract
Systems, methods and computer program products for providing indirect data addressing at an I/O subsystem of an I/O processing system. The computer program product includes a tangible storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method. The method includes receiving a control word for an I/O operation. The control word includes an indirect data address for data associated with the I/O operation. The indirect data address includes a starting location of a list of storage addresses that collectively specify the data, the list spans two or more non-contiguous storage locations. Data is gathered responsive to the list. The gathered data is transmitted to a control unit in the I/O processing system.
Description
PROVIDING INDIRECT DATA ADDRESSING IN AN INPUT/OUTPUT
PROCESSING SYSTEM WHERE THE INDIRECT DATA ADDRESS LIST
IS NON-CONTIGUOUS
FIELD OF THE INVENTION
The present disclosure relates generally to input/output processing, and in particular, to providing a non-contiguous indirect data addressing list at an I/O subsystem of an I/O
processing system.
DESCRIPTION OF BACKGROUND
Input/output (I/O) operations are used to transfer data between memory and I/O
devices of an I/O processing system. Specifically, data is written from memory to one or more I/O
devices, and data is read from one or more I/O devices to memory by executing I/O
operations.
To facilitate processing of I/O operations, an I/O subsystem of the I/O
processing system is employed. The I/O subsystem is coupled to main memory and the I/O devices of the I/O
processing system and directs the flow of information between memory and the I/O devices.
One example of an I/O subsystem is a channel subsystem. The channel subsystem uses channel paths as communications media. Each channel path includes a channel coupled to a control unit, the control unit being further coupled to one or more I/O
devices.
The channel subsystem may employ channel command words (CCWs) to transfer data between the I/O devices and memory. A CCW specifies the command to be executed. For commands initiating certain I/O operations, the CCW designates the memory area associated with the operation, the action to be taken whenever a transfer to or from the area is completed, and other options.
During I/O processing, a list of CCWs is fetched from memory by a channel. The channel parses each command from the list of CCWs and forwards a number of the commands, each command in its own entity, to a control unit coupled to the channel. The control unit then processes the commands. The channel tracks the state of each command and controls when the next set of commands are to be sent to the control unit for processing.
The channel
PROCESSING SYSTEM WHERE THE INDIRECT DATA ADDRESS LIST
IS NON-CONTIGUOUS
FIELD OF THE INVENTION
The present disclosure relates generally to input/output processing, and in particular, to providing a non-contiguous indirect data addressing list at an I/O subsystem of an I/O
processing system.
DESCRIPTION OF BACKGROUND
Input/output (I/O) operations are used to transfer data between memory and I/O
devices of an I/O processing system. Specifically, data is written from memory to one or more I/O
devices, and data is read from one or more I/O devices to memory by executing I/O
operations.
To facilitate processing of I/O operations, an I/O subsystem of the I/O
processing system is employed. The I/O subsystem is coupled to main memory and the I/O devices of the I/O
processing system and directs the flow of information between memory and the I/O devices.
One example of an I/O subsystem is a channel subsystem. The channel subsystem uses channel paths as communications media. Each channel path includes a channel coupled to a control unit, the control unit being further coupled to one or more I/O
devices.
The channel subsystem may employ channel command words (CCWs) to transfer data between the I/O devices and memory. A CCW specifies the command to be executed. For commands initiating certain I/O operations, the CCW designates the memory area associated with the operation, the action to be taken whenever a transfer to or from the area is completed, and other options.
During I/O processing, a list of CCWs is fetched from memory by a channel. The channel parses each command from the list of CCWs and forwards a number of the commands, each command in its own entity, to a control unit coupled to the channel. The control unit then processes the commands. The channel tracks the state of each command and controls when the next set of commands are to be sent to the control unit for processing.
The channel
2 ensures that each command is sent to the control unit in its own entity.
Further, the channel infers certain information associated with processing the response from the control unit for each command.
Performing I/O processing on a per CCW basis may involve a large amount of processing overhead for the channel subsystem, as the channels parse CCWs, track state information, and react to responses from the control units. Therefore, it may be beneficial to shift much of the processing burden associated with interpreting and managing CCW and state information from the channel subsystem to the control units. Simplifying the role of channels in communicating between the control units and an operating system in the I/O
processing system may increase communication throughput as less handshaking is performed. However, altering command sequences, as well as roles of the channel subsystem and the control units, allows the amount of data that is transferred within a single I/O operation to more than one megabyte. This is the maximum amount of data that can be transferred with one continuous list of transport indirect data addresses when the system page size is 4k bytes. Currently, an existing Channel Command Word (CCW) cannot support a data transfer of more than 64k bytes within a single I/O operation because of the limitation of the two byte count field in the CCW. The Transport Control Word (TCW) solved that problem by increasing the byte count to four bytes in the TCW, but then the next limitation of one megabyte was encountered because the transport indirect data address list (TIDAL) must be contained in one page which is 4k bytes which only allowed 256 address list entries.
BRIEF SUMMARY OF THE INVENTION
Embodiments of the invention include a computer program product for providing indirect data addressing at an input/output (I/O) subsystem of an I/O processing system. The computer program product includes a tangible storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method. The method includes receiving a control word for an I/O operation. The control word includes an indirect data address for data associated with the I/O
operation. The indirect data address includes a starting location of a list of storage addresses that collectively specify the data, the list spans two or more non-contiguous storage locations.
Further, the channel infers certain information associated with processing the response from the control unit for each command.
Performing I/O processing on a per CCW basis may involve a large amount of processing overhead for the channel subsystem, as the channels parse CCWs, track state information, and react to responses from the control units. Therefore, it may be beneficial to shift much of the processing burden associated with interpreting and managing CCW and state information from the channel subsystem to the control units. Simplifying the role of channels in communicating between the control units and an operating system in the I/O
processing system may increase communication throughput as less handshaking is performed. However, altering command sequences, as well as roles of the channel subsystem and the control units, allows the amount of data that is transferred within a single I/O operation to more than one megabyte. This is the maximum amount of data that can be transferred with one continuous list of transport indirect data addresses when the system page size is 4k bytes. Currently, an existing Channel Command Word (CCW) cannot support a data transfer of more than 64k bytes within a single I/O operation because of the limitation of the two byte count field in the CCW. The Transport Control Word (TCW) solved that problem by increasing the byte count to four bytes in the TCW, but then the next limitation of one megabyte was encountered because the transport indirect data address list (TIDAL) must be contained in one page which is 4k bytes which only allowed 256 address list entries.
BRIEF SUMMARY OF THE INVENTION
Embodiments of the invention include a computer program product for providing indirect data addressing at an input/output (I/O) subsystem of an I/O processing system. The computer program product includes a tangible storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method. The method includes receiving a control word for an I/O operation. The control word includes an indirect data address for data associated with the I/O
operation. The indirect data address includes a starting location of a list of storage addresses that collectively specify the data, the list spans two or more non-contiguous storage locations.
3 Data is gathered responsive to the list. The gathered data is transmitted to a control unit in the I/O processing system.
Additional embodiments include an apparatus for providing indirect data addressing at an I/O subsystem of an I/O processing system. The apparatus includes an I/O
subsystem adapted to communicate with a control unit in the I/O processing system. The I/O
subsystem performs a method including receiving a control word for an I/O
operation. The control word includes an indirect data address for data associated with the I/O operation.
The indirect data address includes a starting location of a list of storage addresses that collectively specify the data, the list spans two or more non-contiguous storage locations.
Data is gathered responsive to the list. The gathered data is transmitted to the control unit.
Further embodiments include a method for providing indirect data addressing at an I/O
subsystem of an I/O processing system. The method includes receiving a control word for an I/O operation. The control word includes an indirect data address for data associated with the I/O operation. The indirect data address includes a starting location of a list of storage addresses that collectively specify the data, the list spans two or more non-contiguous storage locations. Data is gathered responsive to the list. The gathered data is transmitted to a control unit in the I/O processing system.
Still further embodiments include a computer program product for providing indirect data addressing at an I/O subsystem of an I/O processing system. The computer program product includes a tangible storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method. The method includes receiving a control word for an I/O operation. The control word includes an indirect data address for customer data output from the I/O operation. The indirect data address includes a starting location of a list of storage addresses that collectively specify a storage location for the customer data output, the list spans two or more non-contiguous storage locations.
Customer data output is received from a control unit in the I/O processing system in response to the I/O operation being executed at the control unit. The customer data output is stored at the storage location at the I/O subsystem responsive to the list.
Other articles of manufacture, apparatuses, and/or methods according to embodiments will be or become apparent to one with skill in the art upon review of the following drawings and
Additional embodiments include an apparatus for providing indirect data addressing at an I/O subsystem of an I/O processing system. The apparatus includes an I/O
subsystem adapted to communicate with a control unit in the I/O processing system. The I/O
subsystem performs a method including receiving a control word for an I/O
operation. The control word includes an indirect data address for data associated with the I/O operation.
The indirect data address includes a starting location of a list of storage addresses that collectively specify the data, the list spans two or more non-contiguous storage locations.
Data is gathered responsive to the list. The gathered data is transmitted to the control unit.
Further embodiments include a method for providing indirect data addressing at an I/O
subsystem of an I/O processing system. The method includes receiving a control word for an I/O operation. The control word includes an indirect data address for data associated with the I/O operation. The indirect data address includes a starting location of a list of storage addresses that collectively specify the data, the list spans two or more non-contiguous storage locations. Data is gathered responsive to the list. The gathered data is transmitted to a control unit in the I/O processing system.
Still further embodiments include a computer program product for providing indirect data addressing at an I/O subsystem of an I/O processing system. The computer program product includes a tangible storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method. The method includes receiving a control word for an I/O operation. The control word includes an indirect data address for customer data output from the I/O operation. The indirect data address includes a starting location of a list of storage addresses that collectively specify a storage location for the customer data output, the list spans two or more non-contiguous storage locations.
Customer data output is received from a control unit in the I/O processing system in response to the I/O operation being executed at the control unit. The customer data output is stored at the storage location at the I/O subsystem responsive to the list.
Other articles of manufacture, apparatuses, and/or methods according to embodiments will be or become apparent to one with skill in the art upon review of the following drawings and
4 detailed description. It is intended that all such additional articles of manufacture, apparatuses, and/or methods be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.
BRIEF DESCRIPTION OF THE DRAWINGS
The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
FIG. 1 depicts one embodiment of an I/O processing system incorporating and using one or more aspects of the present invention;
FIG. 2A depicts one example of a prior art channel command word;
FIG. 2B depicts one example of a prior art channel command word channel program;
FIG. 3 depicts one embodiment of a prior art link protocol used in communicating between a channel and control unit to execute the channel command word channel program of FIG. 2B;
FIG. 4 depicts one embodiment of a transport control word channel program, in accordance with an aspect of the present invention;
FIG. 5 depicts one embodiment of a link protocol used to communicate between a channel and control unit to execute the transport control word channel program of FIG.
4, in accordance with an aspect of the present invention;
FIG. 6 depicts one embodiment of a prior art link protocol used to communicate between a channel and control unit in order to execute four write commands of a channel command word channel program;
FIG. 7 depicts one embodiment of a link protocol used to communicate between a channel and control unit to process the four write commands of a transport control word channel program, in accordance with an aspect of the present invention;
FIG. 8 depicts one embodiment of a control unit and a channel subsystem, in accordance with an aspect of the present invention;
FIG. 9 depicts one embodiment of a transport mode indirect data address word (TIDAW), in accordance with an aspect of the present invention;
FIG. 10 depicts one embodiment of a process for providing non-contiguous indirect data addressing at an I/O subsystem; and FIG. 11 depicts one embodiment of an article of manufacture incorporating one or more aspects of the present invention.
The detailed description explains the preferred embodiments of the invention, together with advantages and features, by way of example with reference to the drawings.
DETAILED DESCRIPTION OF THE INVENTION
In accordance with an aspect of the present invention, input/output (I/O) processing is facilitated. I/O processing is facilitated, in one example, by reducing communications between components of an I/O processing system used to perform the I/O
processing. For instance, the number of exchanges and sequences between an I/O communications adapter, such as a channel, and a control unit is reduced. This is accomplished by sending a plurality of commands from the I/O communications adapter to the control unit as a single entity for execution by the control unit, and by the control unit sending the data resulting from the commands, if any, as a single entity.
The plurality of commands are included in a block, referred to herein as a transport command control block (TCCB), an address of which is specified in a transport control word (TCW). The TCW is sent from an operating system (OS) or other application to the I/O
communications adapter, which in turn forwards the TCCB in a command message to the control unit for processing. The control unit processes each of the commands absent a tracking of status relative to those individual commands by the I/O
communications adapter.
The plurality of commands is also referred to as a channel program, which is parsed and executed on the control unit rather than the I/O communications adapter.
In an exemplary embodiment, the TCW for an I/O operation includes pointers indicating the location of the control data (e.g., the TCCB) and the customer data associated with the I/O
operation. In an exemplary embodiment, the pointers refer to an indirect data address, referred to herein as a transport mode indirect data address list (TIDAL). The TIDAL
includes a list of addresses where the data is located; these addresses are referred to herein as transport mode indirect data address words (TIDAWs). In the current system design with 4K pages the TIDAL cannot be larger than four kilobytes (4K), thus limiting the number of continuous TIDAWs that may be included in a single TIDAL to 256 (each TIDAL is bytes). This limits the total amount of data that can be transferred by one I/O operation to one megabyte assuming 4K pages, each TIDAL is 16 bytes and the TIDAL has to be contained in one 4K page. In an exemplary embodiment of the present invention, this limitation is removed by allowing a TIDAW address to indicate the starting location of the next TIDAWs at another storage location which may be in a different page. A
flag in the TIDAW is utilized to indicate whether the address of the TIDAW includes a data address or an address of the continuation of the TIDAW list. In this manner, TIDAWs making up a single TIDAL can be located in non-contiguous storage locations and thus, more than 256 TIDAWs can be included in a single TIDAL list. This allows more data to be transferred within a single I/O operation. For example, in an exemplary embodiment, where the count field in the TCW is four bytes, about four gigabytes (four gigabytes minus one byte) may be transferred within a single I/O operation.
One example of an I/O processing system incorporating and using one or more aspects of the present invention is described with reference to FIG. 1. I/O processing system 100 includes a host system 101, which further includes for instance, a main memory 102, one or more central processing units (CPUs) 104, a storage control element 106, and a channel subsystem 108. The host system 101 may be a large scale computing system, such as a mainframe or server. The I/O processing system 100 also includes one or more control units 110 and one or more I/O devices 112, each of which is described below.
Main memory 102 stores data and programs, which can be input from I/O devices 112. For example, the main memory 102 may include one or more operating systems (OSs) 103 that are executed by one or more of the CPUs 104. For example, one CPU 104 can execute a Linux operating system 103 and a z/OS operating system 103 as different virtual machine instances. The main memory 102 is directly addressable and provides for high-speed processing of data by the CPUs 104 and the channel subsystem 108.
CPU 104 is the controlling center of the I/O processing system 100. It contains sequencing and processing facilities for instruction execution, interruption action, timing functions, initial program loading, and other machine-related functions. CPU 104 is coupled to the storage control element 106 via a connection 114, such as a bidirectional or unidirectional bus.
Storage control element 106 is coupled to the main memory 102 via a connection 116, such as a bus; to CPUs 104 via connection 114; and to channel subsystem 108 via a connection 118. Storage control element 106 controls, for example, queuing and execution of requests made by CPU 104 and channel subsystem 108.
In an exemplary embodiment, channel subsystem 108 provides a communication interface between host system 101 and control units 110. Channel subsystem 108 is coupled to storage control element 106, as described above, and to each of the control units 110 via a connection 120, such as a serial link. Connection 120 may be implemented as an optical link, employing single-mode or multi-mode waveguides in a Fibre Channel fabric. Channel subsystem 108 directs the flow of information between I/O devices 112 and main memory 102. It relieves the CPUs 104 of the task of communicating directly with the I/O devices 112 and permits data processing to proceed concurrently with I/O processing.
The channel subsystem 108 uses one or more channel paths 122 as the communication links in managing the flow of information to or from I/O devices 112. As a part of the I/O
processing, channel subsystem 108 also performs the path-management functions of testing for channel path availability, selecting an available channel path 122 and initiating execution of the operation with the I/O devices 112.
Each channel path 122 includes a channel 124 (channels 124 are located within the channel subsystem 108, in one example, as shown in FIG. 1), one or more control units 110 and one or more connections 120. In another example, it is also possible to have one or more dynamic switches (not depicted) as part of the channel path 122. A dynamic switch is coupled to a channel 124 and a control unit 110 and provides the capability of physically interconnecting any two links that are attached to the switch. In another example, it is also possible to have multiple systems, and therefore multiple channel subsystems (not depicted) attached to control unit 110.
Also located within channel subsystem 108 are subchannels (not shown). One subchannel is provided for and dedicated to each I/O device 112 accessible to a program through the channel subsystem 108. A subchannel (e.g., a data structure, such as a table) provides the logical appearance of a device to the program. Each subchannel provides information concerning the associated I/O device 112 and its attachment to channel subsystem 108. The subchannel also provides information concerning I/O operations and other functions involving the associated I/O device 112. The subchannel is the means by which channel subsystem 108 provides information about associated I/O devices 112 to CPUs 104, which obtain this information by executing I/O instructions.
Channel subsystem 108 is coupled to one or more control units 110. Each control unit 110 provides logic to operate and control one or more I/O devices 112 and adapts, through the use of common facilities, the characteristics of each I/O device 112 to the link interface provided by the channel 124. The common facilities provide for the execution of I/O
operations, indications concerning the status of the I/O device 112 and control unit 110, control of the timing of data transfers over the channel path 122 and certain levels of I/O
device 112 control.
Each control unit 110 is attached via a connection 126 (e.g., a bus) to one or more I/O
devices 112. I/O devices 112 receive information or store information in main memory 102 and/or other memory. Examples of I/O devices 112 include card readers and punches, magnetic tape units, direct access storage devices, displays, keyboards, printers, pointing devices, teleprocessing devices, communication controllers and sensor based equipment, to name a few.
One or more of the above components of the I/O processing system 100 are further described in "IBM z/Architecture Principles of Operation," Publication No. SA22-7832-05, 6th Edition, April 2007; U.S. Patent No. 5,461,721 entitled "System For Transferring Data Between I/O Devices And Main Or Expanded Storage Under Dynamic Control Of Independent Indirect Address Words (IDAWS)," Cormier et al., issued October 24, 1995;
and U.S. Patent No. 5,526,484 entitled "Method And System For Pipelining The Processing Of Channel Command Words," Casper et al., issued June 11, 1996, each of which is hereby incorporated herein by reference in its entirety. IBM is a registered trademark of International Business Machines Corporation, Armonk, New York, USA. Other names used herein may be registered trademarks, trademarks or product names of International Business Machines Corporation or other companies.
In one embodiment, to transfer data between I/O devices 112 and memory 102, channel command words (CCWs) are used. A CCW specifies the command to be executed, and includes other fields to control processing. One example of a CCW is described with reference to FIG. 2A. A CCW 200 includes, for instance, a command code 202 specifying the command to be executed (e.g., read, read backward, control, sense and write); a plurality of flags 204 used to control the I/O operation; for commands that specify the transfer of data, a count field 206 that specifies the number of bytes in the storage area designated by the CCW to be transferred; and a data address 208 that points to a location in main memory that includes data, when direct addressing is employed, or to a list (e.g., contiguous list) of modified indirect data address words (MIDAWs) to be processed, when modified indirect data addressing is employed. Modified indirect addressing is further described in U.S.
Application Serial Number 11/464,613, entitled "Flexibly Controlling The Transfer Of Data Between Input/Output Devices And Memory," Brice et al., filed August 15, 2006, which is hereby incorporated herein by reference in its entirety.
One or more CCWs arranged for sequential execution form a channel program, also referred to herein as a CCW channel program. The CCW channel program is set up by, for instance, an operating system, or other software. The software sets up the CCWs and obtains the addresses of memory assigned to the channel program. An example of a CCW
channel program is described with reference to FIG. 2B. A CCW channel program 210 includes, for instance, a define extent CCW 212 that has a pointer 214 to a location in memory of define extent data 216 to be used with the define extent command. In this example, a transfer in channel (TIC) 218 follows the define extent command that refers the channel program to another area in memory (e.g., an application area) that includes one or more other CCWs, such as a locate record 217 that has a pointer 219 to locate record data 220, and one or more write CCWs 221. Each write CCW 220 has a pointer 222 to a data area 224. The data area includes an address to directly access the data or a list of data address words (e.g., MIDAWs or IDAWs) to indirectly access the data. Further, CCW channel program 210 includes a predetermined area in the channel subsystem defined by the device address called the subchannel for status 226 resulting from execution of the CCW channel program.
The processing of a CCW channel program is described with reference to FIG. 3, as well as with reference to FIG. 2B. In particular, FIG. 3 shows an example of the various exchanges and sequences that occur between a channel and a control unit when a CCW
channel program is executing. The link protocol used for the communications is FICON
(Fibre Connectivity), in this example. Information regarding FICON is described in "Fibre Channel Single Byte Command Code Sets-3 Mapping Protocol (FC-SB-3), T1l/Project 1357-D/Rev. 1.6, INCITS (March 2003), which is hereby incorporated herein by reference in its entirety.
Referring to FIG. 3, a channel 300 opens an exchange with a control unit 302 and sends a define extent command and data associated therewith 304 to control unit 302.
The command is fetched from define extent CCW 212 (FIG. 2B) and the data is obtained from define extent data area 216. The channel 300 uses TIC 218 to locate the locate record CCW
and the write CCW. It fetches the locate record command and data 306 (FIG. 3) from the locate record CCW 217 (FIG. 2B) and locate record data 220. The write command and data 308 (FIG. 3) is fetched from write CCW 221 and data area 224 (FIG. 2B). Each is sent to the control unit 302.
The control unit 302 opens an exchange 310 with the channel 300, in response to the open exchange of the channel 300. This can occur before or after locate command and data 306 and/or write command and data 308. Along with the open exchange, a response (CMR) is forwarded to the channel 300. The CMR provides an indication to the channel 300 that the control unit 302 is active and operating.
The control unit 302 provides the status to the channel 300 and closes the exchange 312. In response thereto, the channel 300 stores the data, examines the status and closes the exchange 314, which indicates to the control unit 302 that the status has been received.
The processing of the above CCW channel program to write 4k of data requires two exchanges to be opened and closed and six sequences. The total number of exchanges and sequences between the channel and control unit is reduced through collapsing multiple commands of the channel program into a TCCB. The channel, e.g., channel 124 of FIG. 1, uses a TCW to identify the location of the TCCB, as well as locations for accessing and storing status and data associated with executing the channel program. The TCW
is interpreted by the channel and is not sent or seen by the control unit.
One example of a channel program to write 4k of data, as in FIG. 2B, but includes a TCCB, instead of separate individual CCWs, is described with reference to FIG. 4. As shown, a channel program 400, referred to herein as a TCW channel program, includes a specifying a location in memory of a TCCB 404, as well as a location in memory of a data area 406 or a TIDAL 410 (i.e., a list of transport mode indirect data address words (TIDAWs), similar to MIDAWs) that points to data area 406, and a status area 408. TIDAW
zero 412, TIDAW one 414 and TIDAW two 416 (collectively TIDAWs 412 - 416) can reference different locations in the data area 406 for acquiring or storing data. The TIDAWs 412 - 416 can reference non-contiguous blocks of data or contiguous blocks of data. The TIDAWs 412 - 416 in TIDAL 410 may be located sequentially in memory or located non-contiguously relative to each other. While only three TIDAWs 412 - 416 are depicted in TIDAL 410, it will be understood that any number of TIDAWs can be included in the TIDAL 410.
The processing of a TCW channel program is described with reference to FIG. 5.
The link protocol used for these communications is, for instance, Fibre Channel Protocol (FCP). In particular, three phases of the FCP link protocol are used, allowing host bus adapters to be used that support FCP to perform data transfers controlled by CCWs. FCP and its phases are described further in "Information Technology - Fibre Channel Protocol for SCSI, Third Version (FCP-3)," T10 Project 1560-D, Revision 4, September 13, 2005, which is hereby incorporated herein by reference in its entirety.
Referring to FIG. 5, a channel 500 opens an exchange with a control unit 502 and sends TCCB 504 to the control unit 502. In one example, the TCCB 504 and sequence initiative are transferred to the control unit 502 in a FCP command, referred to as FCP
CMND
information unit (IU) or a transport command IU. The control unit 502 transmits a transfer ready (XFER-RDY) IU 510 to the channel 500 when it is ready to receive data for the write commands received in the TCCB 504. In response to receiving the XFER-RDY IU
510, the channel 500 transfers the data 506 to the control unit 502, via, for instance, a FCP Data IU.
The control unit 502 executes the multiple commands of the TCCB 504 (e.g., define extent command, locate record command, write command as device control words (DCWs)) and writes the data 506 received from the channel 500. It also provides status and closes the exchange 508. As one example, final status is sent in a FCP status frame that has a bit active in, for instance, byte 10 or 11 of the payload of a FCP_RSP IU, also referred to as a transport response IU. The FCP_RSP IU payload may be used to transport FICON ending status along with additional status information.
The embodiment of the link protocol depicted in FIG. 5 is utilized when XFER_RDY is enabled. In the embodiment depicted in FIG. 5, the channel 500 cannot send the data 506 to the control unit 502 until it is requested by the control unit 502 via the XFER_RDY IU 510.
In an alternate exemplary embodiment, XFER_RDY is disabled and the control unit does not transmit a XFER RDY IU 510 to the channel 500. Thus, the channel 500 does not have to wait for the control unit 502 to request the data 506 before sending the data 506. This alternate embodiment, where XFER_RDY is disabled may be utilized when the channel 500 and the control unit 502 are located geographically far apart from each other (e.g., greater than twenty kilometers, greater than fifty kilometers) to improve performance.
Unless otherwise specified, the discussion herein assumes that XFER_RDY is enabled.
In a further example, to write 4K of customer data, the channel 500 uses the FCP link protocol phases, as follows:
1. Transfer a TCCB in the FCP_CMND IU and sequence initiative to the control unit 502.
2. Wait for a XFER_RDY IU indicating that the control unit is ready to receive the data.
3. Transfer the IU of data, and sequence initiative to the control unit 502.
4. Final status is sent in a FCP status frame that has a bit active in, for instance, byte or 11 of the FCP_RSP IU Payload. The FCP_RSP_INFO field or sense field is used to transport FICON ending status along with additional status information.
By executing the TCW channel program of FIG. 4, there is only one exchange opened and closed (see also FIG. 5), instead of two exchanges for the CCW channel program of FIG. 2B
(see also FIG. 3). Further, for the TCW channel program, there are four communication sequences (see FIGs. 4-5), as compared to six sequences for the CCW channel program (see FIGs. 2B-3).
The number of exchanges and sequences remain the same for a TCW channel program, even if additional commands are added to the program. Compare, for example, the communications of the CCW channel program of FIG. 6 with the communications of the TCW channel program of FIG. 7. In the CCW channel program of FIG. 6, each of the commands (e.g., define extent command and data 600, locate record command and data 601, write command and data 602, write command and data 604, locate record command and data 606, write command and data 608, and write command and data 620) are sent in separate sequences from channel 610 to control unit 612. This CCW channel program requires two exchanges to be opened and closed (e.g., open exchanges 622, 624 and close exchanges 626, 628), and ten communications sequences. This is compared to the four sequences and one exchange for the TCW channel program of FIG. 7, which accomplishes the same task as the CCW channel program of FIG. 6.
As depicted in FIG. 7, a channel 700 opens an exchange with a control unit 702 and sends a TCCB 704 to the control unit 702. The TCCB 704 includes the define extent command, the two locate record commands, and the four write commands in DCWs, as described above.
Similar to the example depicted in FIG. 5, the control unit 702 may use an XFER_RDY IU
710 to notify the channel 700 that it is ready receive data, provided that XFER_RDY support is not disabled. The channel 700 transmits l6k of data 706 to the control unit 702 in a single sequence upon receipt of the XFER_RDY IU 710. The channel 700 inserts a CRC
every 4K
of the l6k of data 706 in the sequence. The insertion of a CRC every 4K allows the control unit 702 to verify the 16K of data incrementally, rather than buffer the entire 16K for verification before completing the write commands in the TCCB 704.
Additionally, the control unit 702 provides status to the channel 700 and closes the exchange 708. Thus, the TCW channel program of FIG. 7 requires much less communications to transfer the same amount of data as the CCW channel program of FIG. 6, while supporting incremental data verification via multiple CRC insertion in the output data stream from the channel 700.
Turning now to FIG. 8, one embodiment of channel 124 in the channel subsystem 108 and the control unit 110 of FIG. 1 that support TCW channel program execution are depicted in greater detail. The control unit 110 includes CU control logic 802 to parse and process messages containing a TCCB, such as the TCCB 704 of FIG. 7, as well as data received from the channel 124 via the connection 120. The CU control logic 802 can extract DCWs and control data from the TCCB received at the control unit 110 to control a device, for instance, I/O device 112 via connection 126. The CU control logic 802 sends device commands and data to the I/O device 112, and receives status information and other feedback from the I/O device 112. When the CU control logic 802 receives data, such as the first checking block boundary of the 16K bytes of data 706 of FIG. 7, the CU
control logic 802 writes this data received into data buffer 804 for temporary storage, until the CRC is received for the checking block boundary is checked, then that data may be sent to the I/O
device 112. This continues for each checking block boundary until the I/O
operation is completed.
The control unit 110 may further include other queue or memory elements (not depicted) for storing additional message or status information associated with communications between the channel 124 and the I/O device 112.
The channel 124 in the channel subsystem 108 includes elements to support communication with the control unit 110. For example, the channel 124 may include CHN
control logic 806 that interfaces with the gather data logic 812. The gather data logic 812 is described herein below in reference to FIG. 10. In an exemplary embodiment, the CHN control logic 806 controls communication between the channel subsystem 108 and the control unit 110. The CHN control logic 806 may directly interface to the CU control logic 802 via the connection 120 to send commands and receive responses, such as transport commands and response IUs. Alternatively, messaging interfaces and/or additional buffers (not depicted) can be placed between the CHN control logic 806 and the CU control logic 802. The CHN
subsystem registers 814 can include fixed values that provide configuration and status information, as well as dynamic status information, updated as commands are transported and responses are received. The CHN subsystem registers 814 may be dedicated hardware registers and/or virtual registers established using memory mapping.
In one embodiment, the CHN subsystem registers 814 include the TIDAL 410 and TIDAWs 412 - 416 of FIG. 4 as memory mapped registers.
One example of a TIDAW 900 is depicted in FIG. 9. The TIDAW 900 provides indirect addressing to data used in a TCW channel program, such as the TIDAWs 412 - 416 of FIG.
4. The TIDAW 900 includes flags 902, a count 904, and an address 906. Each field (i.e., flags 902, count 904, and address 906) in the TIDAW format 900 is assigned to a particular byte address to support parsing of the fields. Although one arrangement of fields within the TIDAW 900 is depicted in FIG. 9, it will be understood that the order of fields can be rearranged to alternate orderings.
In an exemplary embodiment, the flags 902 include a last TIDAW flag and a transport-transfer in channel (T-TIC) flag, in addition to other flags. The last TIDAW
flag indicates that the associated TIDAW is the last TIDAW in a TIDAL, consistent with the definition for a MIDAW. When count 904 goes to zero with the last TIDAW flag set, the data transfer for the associated I/O operation is complete. The T-TIC flag indicates whether the contents of the address 906 include data or the address of the next TIDAW in the TIDAL. In an exemplary embodiment, when the T-TIC flag is set, then the address 906 in the TIDAW is the address of the next TIDAW in the TIDAL. In the manner, the address 906 may be utilized to access a TIDAW at a non-contiguous storage location from the current TIDAW.
Thus, the TIDAW list can contain more than 256 entries, thereby exceeding the maximum number of allowable indirect data address words in current implementations. In an exemplary embodiment, when the T-TIC flag is set the address 906 must have the four low order bits set to zero because the 16 byte TIDAW must be on a 16 byte address boundary.
When the T-TIC flag is not set, then the address 906 in the TIDAW is the address of a portion of the data that makes up the data being gathered for the I/O
operation. The size of the data is indicated in the count field 904. If the last TIDAW flag and the T-TIC flag are not set, then the next TIDAW is located in the next storage location (e.g., it is contiguous to the current TIDAW).
Turning now to FIG. 10, a process 1000 for gathering data for an I/O operation will now be described in accordance with exemplary embodiments, and in reference to the I/O processing system 100 of FIG. 1. At block 1002, the channel subsystem 108 receives a control word for an I/O operation (e.g., a TCW). The control word includes an indirect data address that points to the starting address of a list of storage addresses (e.g,. a TIDAL
having multiple TIDAWs) that make up the data utilized by the by the I/O operation. In exemplary embodiments, the data is customer data (e.g., data input or output from the I/O operation).
In alternate exemplary embodiments, the data is control data (e.g., a TCCB).
In an exemplary embodiment, the list of storage addresses spans two or more non-contiguous storage locations.
At block 1004, the data is gathered by instructions located at the channel subsystem 108.
The gathering is based on the contents of the list. In an exemplary embodiment, each entry in the list (e.g., each TIDAW) includes both a storage address and a T-TIC
flag to indicate whether the storage address is the location of a portion of the data, or whether the storage address points to the location of another portion of the list containing more storage addresses. In this manner, a single TIDAL can be contained in multiple pages removing any restraints on the length of the TIDAL. When the T-TIC flag indicates that the storage address is the location of a portion of the data (e.g., the T-TIC flag is not set), then the data at the storage location is accessed and added to the data. This adding of new data can be performed in any manner known in the art, such as merging with data already gathered, appending to data already gathered, etc.
When the T-TIC flag indicates that the current storage address is the location of another portion of the list, then processing continues by accessing a new TIDAW
located at the specified storage location. Data at the storage location specified in the new TIDAW is accessed and added to the data. In an exemplary embodiment, the TIDAW includes a count 904 to specify how much data to read (or write) from each storage address.
When a TIDAW
with the last TIDAW flag is set the gathering is completed. Otherwise, the next TIDAW is accessed and the data gathering continues.
At block 1006, the data is transmitted to a control unit 110 by the channel subsystem 108.
Technical effects of exemplary embodiments include providing non-contiguous indirect data addressing at a I/O subsystem. By allowing multiple 4k byte pages to contain the list of storage addresses (TIDAL) allows the number of TIDAWs to be unlimited, therefore more data can be associated with a single I/O operation. Large transfers of data can reduce communication overhead by avoiding additional handshaking and other delays associated with multiple smaller messages.
The following examples depict manners in which exemplary embodiments may be utilized to perform more than moving large blocks of data.
Exemplary embodiments may be utilized to aid in the prefixing of a channel program by an operating system. For example, when a channel program is passed to an operating system, the operating system may modify the channel program to add, replace, or modify command CCWs or DCWs. In an exemplary embodiment, this implies that a TCCB TIDAL will be created where the first TIDAW points to an area of storage containing the first part of the modified TCCB. The second TIDAW points to the remainder of the unmodified TCCB.
Exemplary embodiments may also be used to aid in the prefixing of channel programs by a hypervisor. If the hypervisor needs to modify the channel program, it would need to create a TIDAL with one more entry than the one passed by the guest. If the TIDAL
passed by the guest is already the maximum size (256 TIDAWs), then the hypervisor can make its own modifications by creating a TCCB TIDAL that has two TIDAWs, one of which is the T-TICs to the first TIDAW of the TIDAL passed by the guest.
TIDAL T-TICs can also ease storage requirements for operating systems. If the channel program containing a TCCB TIDAL needs to be modified, it takes less storage to create a TIDAW and T-TIC than to allocated storage for the caller's TCCB TIDAL plus one more TIDAW.
As described above, embodiments can be embodied in the form of computer-implemented processes and apparatuses for practicing those processes. In exemplary embodiments, the invention is embodied in computer program code executed by one or more network elements. Embodiments include a computer program product 1100 as depicted in FIG. 11 on a computer usable medium 1102 with computer program code logic 1104 containing instructions embodied in tangible media as an article of manufacture.
Exemplary articles of manufacture for computer usable medium 1102 may include floppy diskettes, CD-ROMs, hard drives, universal serial bus (USB) flash drives, or any other computer-readable storage medium, wherein, when the computer program code logic 1104 is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention.
Embodiments include computer program code logic 1104, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code logic 1104 is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. When implemented on a general-purpose microprocessor, the computer program code logic 1104 segments configure the microprocessor to create specific logic circuits.
While the invention has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof.
Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims. Moreover, the use of the terms first, second, etc. do not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another. Furthermore, the use of the terms a, an, etc. do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced item.
BRIEF DESCRIPTION OF THE DRAWINGS
The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
FIG. 1 depicts one embodiment of an I/O processing system incorporating and using one or more aspects of the present invention;
FIG. 2A depicts one example of a prior art channel command word;
FIG. 2B depicts one example of a prior art channel command word channel program;
FIG. 3 depicts one embodiment of a prior art link protocol used in communicating between a channel and control unit to execute the channel command word channel program of FIG. 2B;
FIG. 4 depicts one embodiment of a transport control word channel program, in accordance with an aspect of the present invention;
FIG. 5 depicts one embodiment of a link protocol used to communicate between a channel and control unit to execute the transport control word channel program of FIG.
4, in accordance with an aspect of the present invention;
FIG. 6 depicts one embodiment of a prior art link protocol used to communicate between a channel and control unit in order to execute four write commands of a channel command word channel program;
FIG. 7 depicts one embodiment of a link protocol used to communicate between a channel and control unit to process the four write commands of a transport control word channel program, in accordance with an aspect of the present invention;
FIG. 8 depicts one embodiment of a control unit and a channel subsystem, in accordance with an aspect of the present invention;
FIG. 9 depicts one embodiment of a transport mode indirect data address word (TIDAW), in accordance with an aspect of the present invention;
FIG. 10 depicts one embodiment of a process for providing non-contiguous indirect data addressing at an I/O subsystem; and FIG. 11 depicts one embodiment of an article of manufacture incorporating one or more aspects of the present invention.
The detailed description explains the preferred embodiments of the invention, together with advantages and features, by way of example with reference to the drawings.
DETAILED DESCRIPTION OF THE INVENTION
In accordance with an aspect of the present invention, input/output (I/O) processing is facilitated. I/O processing is facilitated, in one example, by reducing communications between components of an I/O processing system used to perform the I/O
processing. For instance, the number of exchanges and sequences between an I/O communications adapter, such as a channel, and a control unit is reduced. This is accomplished by sending a plurality of commands from the I/O communications adapter to the control unit as a single entity for execution by the control unit, and by the control unit sending the data resulting from the commands, if any, as a single entity.
The plurality of commands are included in a block, referred to herein as a transport command control block (TCCB), an address of which is specified in a transport control word (TCW). The TCW is sent from an operating system (OS) or other application to the I/O
communications adapter, which in turn forwards the TCCB in a command message to the control unit for processing. The control unit processes each of the commands absent a tracking of status relative to those individual commands by the I/O
communications adapter.
The plurality of commands is also referred to as a channel program, which is parsed and executed on the control unit rather than the I/O communications adapter.
In an exemplary embodiment, the TCW for an I/O operation includes pointers indicating the location of the control data (e.g., the TCCB) and the customer data associated with the I/O
operation. In an exemplary embodiment, the pointers refer to an indirect data address, referred to herein as a transport mode indirect data address list (TIDAL). The TIDAL
includes a list of addresses where the data is located; these addresses are referred to herein as transport mode indirect data address words (TIDAWs). In the current system design with 4K pages the TIDAL cannot be larger than four kilobytes (4K), thus limiting the number of continuous TIDAWs that may be included in a single TIDAL to 256 (each TIDAL is bytes). This limits the total amount of data that can be transferred by one I/O operation to one megabyte assuming 4K pages, each TIDAL is 16 bytes and the TIDAL has to be contained in one 4K page. In an exemplary embodiment of the present invention, this limitation is removed by allowing a TIDAW address to indicate the starting location of the next TIDAWs at another storage location which may be in a different page. A
flag in the TIDAW is utilized to indicate whether the address of the TIDAW includes a data address or an address of the continuation of the TIDAW list. In this manner, TIDAWs making up a single TIDAL can be located in non-contiguous storage locations and thus, more than 256 TIDAWs can be included in a single TIDAL list. This allows more data to be transferred within a single I/O operation. For example, in an exemplary embodiment, where the count field in the TCW is four bytes, about four gigabytes (four gigabytes minus one byte) may be transferred within a single I/O operation.
One example of an I/O processing system incorporating and using one or more aspects of the present invention is described with reference to FIG. 1. I/O processing system 100 includes a host system 101, which further includes for instance, a main memory 102, one or more central processing units (CPUs) 104, a storage control element 106, and a channel subsystem 108. The host system 101 may be a large scale computing system, such as a mainframe or server. The I/O processing system 100 also includes one or more control units 110 and one or more I/O devices 112, each of which is described below.
Main memory 102 stores data and programs, which can be input from I/O devices 112. For example, the main memory 102 may include one or more operating systems (OSs) 103 that are executed by one or more of the CPUs 104. For example, one CPU 104 can execute a Linux operating system 103 and a z/OS operating system 103 as different virtual machine instances. The main memory 102 is directly addressable and provides for high-speed processing of data by the CPUs 104 and the channel subsystem 108.
CPU 104 is the controlling center of the I/O processing system 100. It contains sequencing and processing facilities for instruction execution, interruption action, timing functions, initial program loading, and other machine-related functions. CPU 104 is coupled to the storage control element 106 via a connection 114, such as a bidirectional or unidirectional bus.
Storage control element 106 is coupled to the main memory 102 via a connection 116, such as a bus; to CPUs 104 via connection 114; and to channel subsystem 108 via a connection 118. Storage control element 106 controls, for example, queuing and execution of requests made by CPU 104 and channel subsystem 108.
In an exemplary embodiment, channel subsystem 108 provides a communication interface between host system 101 and control units 110. Channel subsystem 108 is coupled to storage control element 106, as described above, and to each of the control units 110 via a connection 120, such as a serial link. Connection 120 may be implemented as an optical link, employing single-mode or multi-mode waveguides in a Fibre Channel fabric. Channel subsystem 108 directs the flow of information between I/O devices 112 and main memory 102. It relieves the CPUs 104 of the task of communicating directly with the I/O devices 112 and permits data processing to proceed concurrently with I/O processing.
The channel subsystem 108 uses one or more channel paths 122 as the communication links in managing the flow of information to or from I/O devices 112. As a part of the I/O
processing, channel subsystem 108 also performs the path-management functions of testing for channel path availability, selecting an available channel path 122 and initiating execution of the operation with the I/O devices 112.
Each channel path 122 includes a channel 124 (channels 124 are located within the channel subsystem 108, in one example, as shown in FIG. 1), one or more control units 110 and one or more connections 120. In another example, it is also possible to have one or more dynamic switches (not depicted) as part of the channel path 122. A dynamic switch is coupled to a channel 124 and a control unit 110 and provides the capability of physically interconnecting any two links that are attached to the switch. In another example, it is also possible to have multiple systems, and therefore multiple channel subsystems (not depicted) attached to control unit 110.
Also located within channel subsystem 108 are subchannels (not shown). One subchannel is provided for and dedicated to each I/O device 112 accessible to a program through the channel subsystem 108. A subchannel (e.g., a data structure, such as a table) provides the logical appearance of a device to the program. Each subchannel provides information concerning the associated I/O device 112 and its attachment to channel subsystem 108. The subchannel also provides information concerning I/O operations and other functions involving the associated I/O device 112. The subchannel is the means by which channel subsystem 108 provides information about associated I/O devices 112 to CPUs 104, which obtain this information by executing I/O instructions.
Channel subsystem 108 is coupled to one or more control units 110. Each control unit 110 provides logic to operate and control one or more I/O devices 112 and adapts, through the use of common facilities, the characteristics of each I/O device 112 to the link interface provided by the channel 124. The common facilities provide for the execution of I/O
operations, indications concerning the status of the I/O device 112 and control unit 110, control of the timing of data transfers over the channel path 122 and certain levels of I/O
device 112 control.
Each control unit 110 is attached via a connection 126 (e.g., a bus) to one or more I/O
devices 112. I/O devices 112 receive information or store information in main memory 102 and/or other memory. Examples of I/O devices 112 include card readers and punches, magnetic tape units, direct access storage devices, displays, keyboards, printers, pointing devices, teleprocessing devices, communication controllers and sensor based equipment, to name a few.
One or more of the above components of the I/O processing system 100 are further described in "IBM z/Architecture Principles of Operation," Publication No. SA22-7832-05, 6th Edition, April 2007; U.S. Patent No. 5,461,721 entitled "System For Transferring Data Between I/O Devices And Main Or Expanded Storage Under Dynamic Control Of Independent Indirect Address Words (IDAWS)," Cormier et al., issued October 24, 1995;
and U.S. Patent No. 5,526,484 entitled "Method And System For Pipelining The Processing Of Channel Command Words," Casper et al., issued June 11, 1996, each of which is hereby incorporated herein by reference in its entirety. IBM is a registered trademark of International Business Machines Corporation, Armonk, New York, USA. Other names used herein may be registered trademarks, trademarks or product names of International Business Machines Corporation or other companies.
In one embodiment, to transfer data between I/O devices 112 and memory 102, channel command words (CCWs) are used. A CCW specifies the command to be executed, and includes other fields to control processing. One example of a CCW is described with reference to FIG. 2A. A CCW 200 includes, for instance, a command code 202 specifying the command to be executed (e.g., read, read backward, control, sense and write); a plurality of flags 204 used to control the I/O operation; for commands that specify the transfer of data, a count field 206 that specifies the number of bytes in the storage area designated by the CCW to be transferred; and a data address 208 that points to a location in main memory that includes data, when direct addressing is employed, or to a list (e.g., contiguous list) of modified indirect data address words (MIDAWs) to be processed, when modified indirect data addressing is employed. Modified indirect addressing is further described in U.S.
Application Serial Number 11/464,613, entitled "Flexibly Controlling The Transfer Of Data Between Input/Output Devices And Memory," Brice et al., filed August 15, 2006, which is hereby incorporated herein by reference in its entirety.
One or more CCWs arranged for sequential execution form a channel program, also referred to herein as a CCW channel program. The CCW channel program is set up by, for instance, an operating system, or other software. The software sets up the CCWs and obtains the addresses of memory assigned to the channel program. An example of a CCW
channel program is described with reference to FIG. 2B. A CCW channel program 210 includes, for instance, a define extent CCW 212 that has a pointer 214 to a location in memory of define extent data 216 to be used with the define extent command. In this example, a transfer in channel (TIC) 218 follows the define extent command that refers the channel program to another area in memory (e.g., an application area) that includes one or more other CCWs, such as a locate record 217 that has a pointer 219 to locate record data 220, and one or more write CCWs 221. Each write CCW 220 has a pointer 222 to a data area 224. The data area includes an address to directly access the data or a list of data address words (e.g., MIDAWs or IDAWs) to indirectly access the data. Further, CCW channel program 210 includes a predetermined area in the channel subsystem defined by the device address called the subchannel for status 226 resulting from execution of the CCW channel program.
The processing of a CCW channel program is described with reference to FIG. 3, as well as with reference to FIG. 2B. In particular, FIG. 3 shows an example of the various exchanges and sequences that occur between a channel and a control unit when a CCW
channel program is executing. The link protocol used for the communications is FICON
(Fibre Connectivity), in this example. Information regarding FICON is described in "Fibre Channel Single Byte Command Code Sets-3 Mapping Protocol (FC-SB-3), T1l/Project 1357-D/Rev. 1.6, INCITS (March 2003), which is hereby incorporated herein by reference in its entirety.
Referring to FIG. 3, a channel 300 opens an exchange with a control unit 302 and sends a define extent command and data associated therewith 304 to control unit 302.
The command is fetched from define extent CCW 212 (FIG. 2B) and the data is obtained from define extent data area 216. The channel 300 uses TIC 218 to locate the locate record CCW
and the write CCW. It fetches the locate record command and data 306 (FIG. 3) from the locate record CCW 217 (FIG. 2B) and locate record data 220. The write command and data 308 (FIG. 3) is fetched from write CCW 221 and data area 224 (FIG. 2B). Each is sent to the control unit 302.
The control unit 302 opens an exchange 310 with the channel 300, in response to the open exchange of the channel 300. This can occur before or after locate command and data 306 and/or write command and data 308. Along with the open exchange, a response (CMR) is forwarded to the channel 300. The CMR provides an indication to the channel 300 that the control unit 302 is active and operating.
The control unit 302 provides the status to the channel 300 and closes the exchange 312. In response thereto, the channel 300 stores the data, examines the status and closes the exchange 314, which indicates to the control unit 302 that the status has been received.
The processing of the above CCW channel program to write 4k of data requires two exchanges to be opened and closed and six sequences. The total number of exchanges and sequences between the channel and control unit is reduced through collapsing multiple commands of the channel program into a TCCB. The channel, e.g., channel 124 of FIG. 1, uses a TCW to identify the location of the TCCB, as well as locations for accessing and storing status and data associated with executing the channel program. The TCW
is interpreted by the channel and is not sent or seen by the control unit.
One example of a channel program to write 4k of data, as in FIG. 2B, but includes a TCCB, instead of separate individual CCWs, is described with reference to FIG. 4. As shown, a channel program 400, referred to herein as a TCW channel program, includes a specifying a location in memory of a TCCB 404, as well as a location in memory of a data area 406 or a TIDAL 410 (i.e., a list of transport mode indirect data address words (TIDAWs), similar to MIDAWs) that points to data area 406, and a status area 408. TIDAW
zero 412, TIDAW one 414 and TIDAW two 416 (collectively TIDAWs 412 - 416) can reference different locations in the data area 406 for acquiring or storing data. The TIDAWs 412 - 416 can reference non-contiguous blocks of data or contiguous blocks of data. The TIDAWs 412 - 416 in TIDAL 410 may be located sequentially in memory or located non-contiguously relative to each other. While only three TIDAWs 412 - 416 are depicted in TIDAL 410, it will be understood that any number of TIDAWs can be included in the TIDAL 410.
The processing of a TCW channel program is described with reference to FIG. 5.
The link protocol used for these communications is, for instance, Fibre Channel Protocol (FCP). In particular, three phases of the FCP link protocol are used, allowing host bus adapters to be used that support FCP to perform data transfers controlled by CCWs. FCP and its phases are described further in "Information Technology - Fibre Channel Protocol for SCSI, Third Version (FCP-3)," T10 Project 1560-D, Revision 4, September 13, 2005, which is hereby incorporated herein by reference in its entirety.
Referring to FIG. 5, a channel 500 opens an exchange with a control unit 502 and sends TCCB 504 to the control unit 502. In one example, the TCCB 504 and sequence initiative are transferred to the control unit 502 in a FCP command, referred to as FCP
CMND
information unit (IU) or a transport command IU. The control unit 502 transmits a transfer ready (XFER-RDY) IU 510 to the channel 500 when it is ready to receive data for the write commands received in the TCCB 504. In response to receiving the XFER-RDY IU
510, the channel 500 transfers the data 506 to the control unit 502, via, for instance, a FCP Data IU.
The control unit 502 executes the multiple commands of the TCCB 504 (e.g., define extent command, locate record command, write command as device control words (DCWs)) and writes the data 506 received from the channel 500. It also provides status and closes the exchange 508. As one example, final status is sent in a FCP status frame that has a bit active in, for instance, byte 10 or 11 of the payload of a FCP_RSP IU, also referred to as a transport response IU. The FCP_RSP IU payload may be used to transport FICON ending status along with additional status information.
The embodiment of the link protocol depicted in FIG. 5 is utilized when XFER_RDY is enabled. In the embodiment depicted in FIG. 5, the channel 500 cannot send the data 506 to the control unit 502 until it is requested by the control unit 502 via the XFER_RDY IU 510.
In an alternate exemplary embodiment, XFER_RDY is disabled and the control unit does not transmit a XFER RDY IU 510 to the channel 500. Thus, the channel 500 does not have to wait for the control unit 502 to request the data 506 before sending the data 506. This alternate embodiment, where XFER_RDY is disabled may be utilized when the channel 500 and the control unit 502 are located geographically far apart from each other (e.g., greater than twenty kilometers, greater than fifty kilometers) to improve performance.
Unless otherwise specified, the discussion herein assumes that XFER_RDY is enabled.
In a further example, to write 4K of customer data, the channel 500 uses the FCP link protocol phases, as follows:
1. Transfer a TCCB in the FCP_CMND IU and sequence initiative to the control unit 502.
2. Wait for a XFER_RDY IU indicating that the control unit is ready to receive the data.
3. Transfer the IU of data, and sequence initiative to the control unit 502.
4. Final status is sent in a FCP status frame that has a bit active in, for instance, byte or 11 of the FCP_RSP IU Payload. The FCP_RSP_INFO field or sense field is used to transport FICON ending status along with additional status information.
By executing the TCW channel program of FIG. 4, there is only one exchange opened and closed (see also FIG. 5), instead of two exchanges for the CCW channel program of FIG. 2B
(see also FIG. 3). Further, for the TCW channel program, there are four communication sequences (see FIGs. 4-5), as compared to six sequences for the CCW channel program (see FIGs. 2B-3).
The number of exchanges and sequences remain the same for a TCW channel program, even if additional commands are added to the program. Compare, for example, the communications of the CCW channel program of FIG. 6 with the communications of the TCW channel program of FIG. 7. In the CCW channel program of FIG. 6, each of the commands (e.g., define extent command and data 600, locate record command and data 601, write command and data 602, write command and data 604, locate record command and data 606, write command and data 608, and write command and data 620) are sent in separate sequences from channel 610 to control unit 612. This CCW channel program requires two exchanges to be opened and closed (e.g., open exchanges 622, 624 and close exchanges 626, 628), and ten communications sequences. This is compared to the four sequences and one exchange for the TCW channel program of FIG. 7, which accomplishes the same task as the CCW channel program of FIG. 6.
As depicted in FIG. 7, a channel 700 opens an exchange with a control unit 702 and sends a TCCB 704 to the control unit 702. The TCCB 704 includes the define extent command, the two locate record commands, and the four write commands in DCWs, as described above.
Similar to the example depicted in FIG. 5, the control unit 702 may use an XFER_RDY IU
710 to notify the channel 700 that it is ready receive data, provided that XFER_RDY support is not disabled. The channel 700 transmits l6k of data 706 to the control unit 702 in a single sequence upon receipt of the XFER_RDY IU 710. The channel 700 inserts a CRC
every 4K
of the l6k of data 706 in the sequence. The insertion of a CRC every 4K allows the control unit 702 to verify the 16K of data incrementally, rather than buffer the entire 16K for verification before completing the write commands in the TCCB 704.
Additionally, the control unit 702 provides status to the channel 700 and closes the exchange 708. Thus, the TCW channel program of FIG. 7 requires much less communications to transfer the same amount of data as the CCW channel program of FIG. 6, while supporting incremental data verification via multiple CRC insertion in the output data stream from the channel 700.
Turning now to FIG. 8, one embodiment of channel 124 in the channel subsystem 108 and the control unit 110 of FIG. 1 that support TCW channel program execution are depicted in greater detail. The control unit 110 includes CU control logic 802 to parse and process messages containing a TCCB, such as the TCCB 704 of FIG. 7, as well as data received from the channel 124 via the connection 120. The CU control logic 802 can extract DCWs and control data from the TCCB received at the control unit 110 to control a device, for instance, I/O device 112 via connection 126. The CU control logic 802 sends device commands and data to the I/O device 112, and receives status information and other feedback from the I/O device 112. When the CU control logic 802 receives data, such as the first checking block boundary of the 16K bytes of data 706 of FIG. 7, the CU
control logic 802 writes this data received into data buffer 804 for temporary storage, until the CRC is received for the checking block boundary is checked, then that data may be sent to the I/O
device 112. This continues for each checking block boundary until the I/O
operation is completed.
The control unit 110 may further include other queue or memory elements (not depicted) for storing additional message or status information associated with communications between the channel 124 and the I/O device 112.
The channel 124 in the channel subsystem 108 includes elements to support communication with the control unit 110. For example, the channel 124 may include CHN
control logic 806 that interfaces with the gather data logic 812. The gather data logic 812 is described herein below in reference to FIG. 10. In an exemplary embodiment, the CHN control logic 806 controls communication between the channel subsystem 108 and the control unit 110. The CHN control logic 806 may directly interface to the CU control logic 802 via the connection 120 to send commands and receive responses, such as transport commands and response IUs. Alternatively, messaging interfaces and/or additional buffers (not depicted) can be placed between the CHN control logic 806 and the CU control logic 802. The CHN
subsystem registers 814 can include fixed values that provide configuration and status information, as well as dynamic status information, updated as commands are transported and responses are received. The CHN subsystem registers 814 may be dedicated hardware registers and/or virtual registers established using memory mapping.
In one embodiment, the CHN subsystem registers 814 include the TIDAL 410 and TIDAWs 412 - 416 of FIG. 4 as memory mapped registers.
One example of a TIDAW 900 is depicted in FIG. 9. The TIDAW 900 provides indirect addressing to data used in a TCW channel program, such as the TIDAWs 412 - 416 of FIG.
4. The TIDAW 900 includes flags 902, a count 904, and an address 906. Each field (i.e., flags 902, count 904, and address 906) in the TIDAW format 900 is assigned to a particular byte address to support parsing of the fields. Although one arrangement of fields within the TIDAW 900 is depicted in FIG. 9, it will be understood that the order of fields can be rearranged to alternate orderings.
In an exemplary embodiment, the flags 902 include a last TIDAW flag and a transport-transfer in channel (T-TIC) flag, in addition to other flags. The last TIDAW
flag indicates that the associated TIDAW is the last TIDAW in a TIDAL, consistent with the definition for a MIDAW. When count 904 goes to zero with the last TIDAW flag set, the data transfer for the associated I/O operation is complete. The T-TIC flag indicates whether the contents of the address 906 include data or the address of the next TIDAW in the TIDAL. In an exemplary embodiment, when the T-TIC flag is set, then the address 906 in the TIDAW is the address of the next TIDAW in the TIDAL. In the manner, the address 906 may be utilized to access a TIDAW at a non-contiguous storage location from the current TIDAW.
Thus, the TIDAW list can contain more than 256 entries, thereby exceeding the maximum number of allowable indirect data address words in current implementations. In an exemplary embodiment, when the T-TIC flag is set the address 906 must have the four low order bits set to zero because the 16 byte TIDAW must be on a 16 byte address boundary.
When the T-TIC flag is not set, then the address 906 in the TIDAW is the address of a portion of the data that makes up the data being gathered for the I/O
operation. The size of the data is indicated in the count field 904. If the last TIDAW flag and the T-TIC flag are not set, then the next TIDAW is located in the next storage location (e.g., it is contiguous to the current TIDAW).
Turning now to FIG. 10, a process 1000 for gathering data for an I/O operation will now be described in accordance with exemplary embodiments, and in reference to the I/O processing system 100 of FIG. 1. At block 1002, the channel subsystem 108 receives a control word for an I/O operation (e.g., a TCW). The control word includes an indirect data address that points to the starting address of a list of storage addresses (e.g,. a TIDAL
having multiple TIDAWs) that make up the data utilized by the by the I/O operation. In exemplary embodiments, the data is customer data (e.g., data input or output from the I/O operation).
In alternate exemplary embodiments, the data is control data (e.g., a TCCB).
In an exemplary embodiment, the list of storage addresses spans two or more non-contiguous storage locations.
At block 1004, the data is gathered by instructions located at the channel subsystem 108.
The gathering is based on the contents of the list. In an exemplary embodiment, each entry in the list (e.g., each TIDAW) includes both a storage address and a T-TIC
flag to indicate whether the storage address is the location of a portion of the data, or whether the storage address points to the location of another portion of the list containing more storage addresses. In this manner, a single TIDAL can be contained in multiple pages removing any restraints on the length of the TIDAL. When the T-TIC flag indicates that the storage address is the location of a portion of the data (e.g., the T-TIC flag is not set), then the data at the storage location is accessed and added to the data. This adding of new data can be performed in any manner known in the art, such as merging with data already gathered, appending to data already gathered, etc.
When the T-TIC flag indicates that the current storage address is the location of another portion of the list, then processing continues by accessing a new TIDAW
located at the specified storage location. Data at the storage location specified in the new TIDAW is accessed and added to the data. In an exemplary embodiment, the TIDAW includes a count 904 to specify how much data to read (or write) from each storage address.
When a TIDAW
with the last TIDAW flag is set the gathering is completed. Otherwise, the next TIDAW is accessed and the data gathering continues.
At block 1006, the data is transmitted to a control unit 110 by the channel subsystem 108.
Technical effects of exemplary embodiments include providing non-contiguous indirect data addressing at a I/O subsystem. By allowing multiple 4k byte pages to contain the list of storage addresses (TIDAL) allows the number of TIDAWs to be unlimited, therefore more data can be associated with a single I/O operation. Large transfers of data can reduce communication overhead by avoiding additional handshaking and other delays associated with multiple smaller messages.
The following examples depict manners in which exemplary embodiments may be utilized to perform more than moving large blocks of data.
Exemplary embodiments may be utilized to aid in the prefixing of a channel program by an operating system. For example, when a channel program is passed to an operating system, the operating system may modify the channel program to add, replace, or modify command CCWs or DCWs. In an exemplary embodiment, this implies that a TCCB TIDAL will be created where the first TIDAW points to an area of storage containing the first part of the modified TCCB. The second TIDAW points to the remainder of the unmodified TCCB.
Exemplary embodiments may also be used to aid in the prefixing of channel programs by a hypervisor. If the hypervisor needs to modify the channel program, it would need to create a TIDAL with one more entry than the one passed by the guest. If the TIDAL
passed by the guest is already the maximum size (256 TIDAWs), then the hypervisor can make its own modifications by creating a TCCB TIDAL that has two TIDAWs, one of which is the T-TICs to the first TIDAW of the TIDAL passed by the guest.
TIDAL T-TICs can also ease storage requirements for operating systems. If the channel program containing a TCCB TIDAL needs to be modified, it takes less storage to create a TIDAW and T-TIC than to allocated storage for the caller's TCCB TIDAL plus one more TIDAW.
As described above, embodiments can be embodied in the form of computer-implemented processes and apparatuses for practicing those processes. In exemplary embodiments, the invention is embodied in computer program code executed by one or more network elements. Embodiments include a computer program product 1100 as depicted in FIG. 11 on a computer usable medium 1102 with computer program code logic 1104 containing instructions embodied in tangible media as an article of manufacture.
Exemplary articles of manufacture for computer usable medium 1102 may include floppy diskettes, CD-ROMs, hard drives, universal serial bus (USB) flash drives, or any other computer-readable storage medium, wherein, when the computer program code logic 1104 is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention.
Embodiments include computer program code logic 1104, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code logic 1104 is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. When implemented on a general-purpose microprocessor, the computer program code logic 1104 segments configure the microprocessor to create specific logic circuits.
While the invention has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof.
Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims. Moreover, the use of the terms first, second, etc. do not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another. Furthermore, the use of the terms a, an, etc. do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced item.
Claims (10)
1. A method for providing indirect data addressing at an I/O subsystem of an I/O
processing system, the method comprising:
receiving a control word for an I/O operation at the I/O subsystem, the control word including an indirect data address for data associated with the I/O operation, the indirect data address including a starting location of a list of storage addresses that collectively specify the data, the list spanning two or more non-contiguous storage locations;
gathering the data responsive to the list; and transmitting the gathered data to a control unit in the I/O processing system;
wherein the list further includes a flag associated with each storage address in the list, the flag having a first value to indicate that the associated storage address refers to a portion of the data and the flag having a second value to indicate that the associated storage address refers to a storage location where additional storage addresses in the list are located; and wherein for each storage address on the list, the gathering includes:
accessing the storage address and the flag associated with the storage address;
adding contents from the storage address to the data in response to the flag having the first value; and accessing a second storage address and a second flag located at the storage address in response to the flag having the second value, and adding contents from the second storage address to the data in response to the second flag having the first value.
processing system, the method comprising:
receiving a control word for an I/O operation at the I/O subsystem, the control word including an indirect data address for data associated with the I/O operation, the indirect data address including a starting location of a list of storage addresses that collectively specify the data, the list spanning two or more non-contiguous storage locations;
gathering the data responsive to the list; and transmitting the gathered data to a control unit in the I/O processing system;
wherein the list further includes a flag associated with each storage address in the list, the flag having a first value to indicate that the associated storage address refers to a portion of the data and the flag having a second value to indicate that the associated storage address refers to a storage location where additional storage addresses in the list are located; and wherein for each storage address on the list, the gathering includes:
accessing the storage address and the flag associated with the storage address;
adding contents from the storage address to the data in response to the flag having the first value; and accessing a second storage address and a second flag located at the storage address in response to the flag having the second value, and adding contents from the second storage address to the data in response to the second flag having the first value.
2. The method of claim 1 wherein a second storage address in the list is located contiguously to a first storage address in the list when the flag has the first value, and the second storage address is located non-contiguously to the first storage address when the flag has the second value.
3. The method of claim 1 wherein the list further includes a count field associated with each storage address in the list, the count field indicating a number of bytes to read from the storage address and the gathering is responsive to the count fields and to the storage addresses.
4. The method of claim 1 wherein the data includes control data.
5. The method of claim 1 wherein the data includes customer data.
6. The method of claim 1 wherein the control word is a transport control word (TCW), the list of storage addresses is a transport indirect data address list (TIDAL), and each storage address is a transport indirect data address word (TIDAW).
7. The method of claim 1 wherein the I/O subsystem is a channel subsystem.
8. The method of claim 1 wherein the control word includes a flag to indicate that it includes an indirect data address.
9. A system comprising means adapted for carrying out all the steps of the method according to any preceding method claim.
10. A computer program comprising instructions for carrying out all the steps of the method according to any preceding method claim, when said computer program is executed on a computer system.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/031,038 US7890668B2 (en) | 2008-02-14 | 2008-02-14 | Providing indirect data addressing in an input/output processing system where the indirect data address list is non-contiguous |
US12/031,038 | 2008-02-14 | ||
PCT/EP2009/051485 WO2009101067A2 (en) | 2008-02-14 | 2009-02-10 | Providing indirect data addressing in an input/output processing system where the indirect data address list is non-contiguous |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2704138A1 true CA2704138A1 (en) | 2009-08-20 |
CA2704138C CA2704138C (en) | 2017-11-07 |
Family
ID=40849165
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2704138A Active CA2704138C (en) | 2008-02-14 | 2009-02-10 | Providing indirect data addressing in an input/output processing system where the indirect data address list is non-contiguous |
Country Status (18)
Country | Link |
---|---|
US (5) | US7890668B2 (en) |
EP (1) | EP2176771B1 (en) |
JP (1) | JP5181141B2 (en) |
KR (1) | KR101174997B1 (en) |
CN (1) | CN101946242B (en) |
AT (1) | ATE492847T1 (en) |
BR (1) | BRPI0908825B1 (en) |
CA (1) | CA2704138C (en) |
CY (1) | CY1111135T1 (en) |
DE (1) | DE602009000463D1 (en) |
DK (1) | DK2176771T3 (en) |
ES (1) | ES2358314T3 (en) |
IL (1) | IL207119A (en) |
PL (1) | PL2176771T3 (en) |
PT (1) | PT2176771E (en) |
RU (1) | RU2505851C2 (en) |
SI (1) | SI2176771T1 (en) |
WO (1) | WO2009101067A2 (en) |
Families Citing this family (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7500023B2 (en) | 2006-10-10 | 2009-03-03 | International Business Machines Corporation | Facilitating input/output processing by using transport control words to reduce input/output communications |
US7502873B2 (en) | 2006-10-10 | 2009-03-10 | International Business Machines Corporation | Facilitating access to status and measurement data associated with input/output processing |
US7908403B2 (en) | 2008-02-14 | 2011-03-15 | International Business Machines Corporation | Reserved device access contention reduction |
US7937507B2 (en) | 2008-02-14 | 2011-05-03 | International Business Machines Corporation | Extended measurement word determination at a channel subsystem of an I/O processing system |
US8176222B2 (en) * | 2008-02-14 | 2012-05-08 | International Business Machines Corporation | Early termination of an I/O operation in an I/O processing system |
US7840718B2 (en) | 2008-02-14 | 2010-11-23 | International Business Machines Corporation | Processing of data to suspend operations in an input/output processing log-out system |
US7904605B2 (en) | 2008-02-14 | 2011-03-08 | International Business Machines Corporation | Computer command and response for determining the state of an I/O operation |
US8478915B2 (en) | 2008-02-14 | 2013-07-02 | International Business Machines Corporation | Determining extended capability of a channel path |
US8108570B2 (en) | 2008-02-14 | 2012-01-31 | International Business Machines Corporation | Determining the state of an I/O operation |
US7917813B2 (en) | 2008-02-14 | 2011-03-29 | International Business Machines Corporation | Exception condition determination at a control unit in an I/O processing system |
US7941570B2 (en) | 2008-02-14 | 2011-05-10 | International Business Machines Corporation | Bi-directional data transfer within a single I/O operation |
US8001298B2 (en) | 2008-02-14 | 2011-08-16 | International Business Machines Corporation | Providing extended measurement data in an I/O processing system |
US7840717B2 (en) | 2008-02-14 | 2010-11-23 | International Business Machines Corporation | Processing a variable length device command word at a control unit in an I/O processing system |
US8082481B2 (en) | 2008-02-14 | 2011-12-20 | International Business Machines Corporation | Multiple CRC insertion in an output data stream |
US9052837B2 (en) | 2008-02-14 | 2015-06-09 | International Business Machines Corporation | Processing communication data in a ships passing condition |
US8166206B2 (en) | 2008-02-14 | 2012-04-24 | International Business Machines Corporation | Cancel instruction and command for determining the state of an I/O operation |
US8214562B2 (en) | 2008-02-14 | 2012-07-03 | International Business Machines Corporation | Processing of data to perform system changes in an input/output processing system |
US8312189B2 (en) | 2008-02-14 | 2012-11-13 | International Business Machines Corporation | Processing of data to monitor input/output operations |
US8117347B2 (en) | 2008-02-14 | 2012-02-14 | International Business Machines Corporation | Providing indirect data addressing for a control block at a channel subsystem of an I/O processing system |
US8196149B2 (en) | 2008-02-14 | 2012-06-05 | International Business Machines Corporation | Processing of data to determine compatability in an input/output processing system |
US8095847B2 (en) | 2008-02-14 | 2012-01-10 | International Business Machines Corporation | Exception condition handling at a channel subsystem in an I/O processing system |
US7899944B2 (en) | 2008-02-14 | 2011-03-01 | International Business Machines Corporation | Open exchange limiting in an I/O processing system |
US7890668B2 (en) | 2008-02-14 | 2011-02-15 | International Business Machines Corporation | Providing indirect data addressing in an input/output processing system where the indirect data address list is non-contiguous |
US7937504B2 (en) | 2008-07-31 | 2011-05-03 | International Business Machines Corporation | Transport control channel program message pairing |
US7904606B2 (en) | 2008-07-31 | 2011-03-08 | International Business Machines Corporation | Transport control channel program chain linked branching |
US8055807B2 (en) * | 2008-07-31 | 2011-11-08 | International Business Machines Corporation | Transport control channel program chain linking including determining sequence order |
US8332542B2 (en) | 2009-11-12 | 2012-12-11 | International Business Machines Corporation | Communication with input/output system devices |
US8677027B2 (en) | 2011-06-01 | 2014-03-18 | International Business Machines Corporation | Fibre channel input/output data routing system and method |
US8364854B2 (en) | 2011-06-01 | 2013-01-29 | International Business Machines Corporation | Fibre channel input/output data routing system and method |
US9021155B2 (en) | 2011-06-01 | 2015-04-28 | International Business Machines Corporation | Fibre channel input/output data routing including discarding of data transfer requests in response to error detection |
US8583988B2 (en) | 2011-06-01 | 2013-11-12 | International Business Machines Corporation | Fibre channel input/output data routing system and method |
US8364853B2 (en) | 2011-06-01 | 2013-01-29 | International Business Machines Corporation | Fibre channel input/output data routing system and method |
US8738811B2 (en) | 2011-06-01 | 2014-05-27 | International Business Machines Corporation | Fibre channel input/output data routing system and method |
US9116788B2 (en) * | 2011-06-10 | 2015-08-25 | International Business Machines Corporation | Using extended asynchronous data mover indirect data address words |
US8346978B1 (en) | 2011-06-30 | 2013-01-01 | International Business Machines Corporation | Facilitating transport mode input/output operations between a channel subsystem and input/output devices |
US8473641B2 (en) | 2011-06-30 | 2013-06-25 | International Business Machines Corporation | Facilitating transport mode input/output operations between a channel subsystem and input/output devices |
US8549185B2 (en) | 2011-06-30 | 2013-10-01 | International Business Machines Corporation | Facilitating transport mode input/output operations between a channel subsystem and input/output devices |
US8312176B1 (en) * | 2011-06-30 | 2012-11-13 | International Business Machines Corporation | Facilitating transport mode input/output operations between a channel subsystem and input/output devices |
US8918542B2 (en) | 2013-03-15 | 2014-12-23 | International Business Machines Corporation | Facilitating transport mode data transfer between a channel subsystem and input/output devices |
US8990439B2 (en) | 2013-05-29 | 2015-03-24 | International Business Machines Corporation | Transport mode data transfer between a channel subsystem and input/output devices |
JP6206006B2 (en) * | 2013-08-30 | 2017-10-04 | 京セラドキュメントソリューションズ株式会社 | Data processing apparatus and image forming apparatus |
CN105426322B (en) * | 2015-12-31 | 2019-05-28 | 华为技术有限公司 | A kind of forecasting method and device of data |
CN107526743B (en) * | 2016-06-21 | 2020-08-07 | 伊姆西Ip控股有限责任公司 | Method and apparatus for compressing file system metadata |
CN115221078A (en) * | 2021-04-14 | 2022-10-21 | 瑞昱半导体股份有限公司 | Data transmission method and data processing circuit |
US11722436B2 (en) | 2021-08-24 | 2023-08-08 | International Business Machines Corporation | Transport control word architecture for physical port mirroring |
Family Cites Families (264)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US625399A (en) * | 1899-05-23 | And carl werder | ||
GB1264096A (en) | 1970-06-27 | 1972-02-16 | ||
US3693161A (en) * | 1970-07-09 | 1972-09-19 | Burroughs Corp | Apparatus for interrogating the availability of a communication path to a peripheral device |
US4004277A (en) * | 1974-05-29 | 1977-01-18 | Gavril Bruce D | Switching system for non-symmetrical sharing of computer peripheral equipment |
US3943283A (en) * | 1974-06-17 | 1976-03-09 | International Business Machines Corporation | Bidirectional single wire data transmission and wrap control |
US4080649A (en) * | 1976-12-16 | 1978-03-21 | Honeywell Information Systems Inc. | Balancing the utilization of I/O system processors |
US4207609A (en) * | 1978-05-08 | 1980-06-10 | International Business Machines Corporation | Method and means for path independent device reservation and reconnection in a multi-CPU and shared device access system |
US4380046A (en) * | 1979-05-21 | 1983-04-12 | Nasa | Massively parallel processor computer |
US4374415A (en) * | 1980-07-14 | 1983-02-15 | International Business Machines Corp. | Host control of suspension and resumption of channel program execution |
US4414644A (en) * | 1981-04-03 | 1983-11-08 | International Business Machines Corporation | Method and apparatus for discarding data from a buffer after reading such data |
US4455605A (en) * | 1981-07-23 | 1984-06-19 | International Business Machines Corporation | Method for establishing variable path group associations and affiliations between "non-static" MP systems and shared devices |
US4497022A (en) * | 1982-10-19 | 1985-01-29 | International Business Machines Corporation | Method and apparatus for measurements of channel operation |
DE3247794A1 (en) * | 1982-12-23 | 1984-06-28 | Max Planck Gesellschaft zur Förderung der Wissenschaften e.V., 3400 Göttingen | REDUCER FOR OPTICAL RADIATION |
US4564903A (en) * | 1983-10-05 | 1986-01-14 | International Business Machines Corporation | Partitioned multiprocessor programming system |
US4779188A (en) * | 1983-12-14 | 1988-10-18 | International Business Machines Corporation | Selective guest system purge control |
US4870566A (en) * | 1984-08-27 | 1989-09-26 | International Business Machines Corp. | Scannerless message concentrator and communications multiplexer |
JPS61123970A (en) | 1984-11-20 | 1986-06-11 | Fujitsu Ltd | Data transmission control system |
US4837677A (en) * | 1985-06-14 | 1989-06-06 | International Business Machines Corporation | Multiple port service expansion adapter for a communications controller |
US4760518A (en) * | 1986-02-28 | 1988-07-26 | Scientific Computer Systems Corporation | Bi-directional databus system for supporting superposition of vector and scalar operations in a computer |
JPS6336461A (en) * | 1986-07-31 | 1988-02-17 | Pfu Ltd | Control system for general-use channel |
JPS63145562A (en) * | 1986-12-09 | 1988-06-17 | Hitachi Ltd | Channel command word readout system for input and output processor |
JPS63236152A (en) | 1987-03-24 | 1988-10-03 | Fujitsu Ltd | I/o queuing control method |
US4926320A (en) * | 1987-04-07 | 1990-05-15 | Nec Corporation | Information processing system having microprogram-controlled type arithmetic processing unit |
US4843541A (en) * | 1987-07-29 | 1989-06-27 | International Business Machines Corporation | Logical resource partitioning of a data processing system |
US4866609A (en) * | 1988-06-22 | 1989-09-12 | International Business Machines Corporation | Byte count handling in serial channel extender with buffering for data pre-fetch |
JPH0283757A (en) | 1988-09-21 | 1990-03-23 | Hitachi Ltd | Communication controlling system |
US5016160A (en) * | 1988-12-15 | 1991-05-14 | International Business Machines Corporation | Computer system having efficient data transfer operations |
US5185736A (en) * | 1989-05-12 | 1993-02-09 | Alcatel Na Network Systems Corp. | Synchronous optical transmission system |
EP0412268B1 (en) * | 1989-08-11 | 1996-09-11 | International Business Machines Corporation | Apparatus for interconnecting a control unit having a parallel bus with a channel having a serial link |
GB9012970D0 (en) * | 1989-09-22 | 1990-08-01 | Ibm | Apparatus and method for asynchronously delivering control elements with pipe interface |
EP0424618A3 (en) * | 1989-10-24 | 1992-11-19 | International Business Machines Corporation | Input/output system |
DE3938520A1 (en) * | 1989-11-21 | 1991-05-29 | Teves Gmbh Alfred | METHOD AND SYSTEM FOR MEASURING DATA EVALUATION AND EVALUATION |
AU650242B2 (en) * | 1989-11-28 | 1994-06-16 | International Business Machines Corporation | Methods and apparatus for dynamically managing input/output (I/O) connectivity |
JPH04649A (en) * | 1990-04-18 | 1992-01-06 | Nec Corp | Fault information transfer system for remote channel device |
CA2037708C (en) * | 1990-05-04 | 1998-01-20 | Richard J. Eickemeyer | General purpose compound apparatus for instruction-level parallel processors |
CA2054026A1 (en) * | 1990-10-31 | 1992-05-01 | William Monroe Turpin | Goal oriented electronic form system |
US5170472A (en) * | 1991-03-28 | 1992-12-08 | International Business Machines Corp. | Dynamically changing a system i/o configuration definition |
US5644712A (en) * | 1991-06-05 | 1997-07-01 | International Business Machines Corporation | Indirect addressing of channels via logical channel groups |
US5386512A (en) * | 1991-07-19 | 1995-01-31 | International Business Machines Corporation | System for deriving and testing mutual capability set after receiving updated capability from other processors and before requesting service information |
JPH0580104A (en) * | 1991-09-20 | 1993-04-02 | Cmk Corp | Manufacture of printed circuit board for motor |
US5805808A (en) | 1991-12-27 | 1998-09-08 | Digital Equipment Corporation | Real time parser for data packets in a communications network |
JPH05204693A (en) * | 1992-01-29 | 1993-08-13 | Fujitsu Ltd | Exceptional order guarantee testing system |
US5301321A (en) | 1992-02-21 | 1994-04-05 | International Business Machines Corporation | Method and system for the minimization of conflicting activities with respect to an object stored within a data processing system |
US5388219A (en) * | 1992-03-02 | 1995-02-07 | International Business Machines Corporation | Efficient channel and control unit for host computer |
JP2532194B2 (en) * | 1992-03-30 | 1996-09-11 | インターナショナル・ビジネス・マシーンズ・コーポレイション | A data processing system having a message routing function between a processor and a coupling function. |
US5317739A (en) * | 1992-03-30 | 1994-05-31 | International Business Machines Corp. | Method and apparatus for coupling data processing systems |
CA2086691C (en) * | 1992-03-30 | 1997-04-08 | David A. Elko | Communicating messages between processors and a coupling facility |
US5600805A (en) * | 1992-06-15 | 1997-02-04 | International Business Machines Corporation | Pass-through for I/O channel subsystem call instructions for accessing shared resources in a computer system having a plurality of operating systems |
US5452455A (en) * | 1992-06-15 | 1995-09-19 | International Business Machines Corporation | Asynchronous command support for shared channels for a computer complex having multiple operating systems |
US5414851A (en) * | 1992-06-15 | 1995-05-09 | International Business Machines Corporation | Method and means for sharing I/O resources by a plurality of operating systems |
US5265240A (en) | 1992-07-24 | 1993-11-23 | International Business Machines Corporation | Channel measurement method and means |
JP2566728B2 (en) * | 1992-10-30 | 1996-12-25 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Logical path scheduling device and execution method |
US5301323A (en) * | 1992-10-30 | 1994-04-05 | International Business Machines Corp. | Data processing system including dynamic channel path management |
JP2840511B2 (en) * | 1992-12-10 | 1998-12-24 | 富士通株式会社 | Error recovery processing apparatus and method for subsystem using magnetic tape device |
US5526484A (en) * | 1992-12-10 | 1996-06-11 | International Business Machines Corporation | Method and system for pipelining the processing of channel command words |
US5528755A (en) * | 1992-12-22 | 1996-06-18 | International Business Machines Corporation | Invalid data detection, recording and nullification |
US5517670A (en) * | 1992-12-30 | 1996-05-14 | International Business Machines Corporation | Adaptive data transfer channel employing extended data block capability |
US5461721A (en) * | 1993-04-14 | 1995-10-24 | International Business Machines Corporation | System for transferring data between I/O devices and main or expanded storage under dynamic control of independent indirect address words (IDAWs) |
US5465359A (en) * | 1993-11-01 | 1995-11-07 | International Business Machines Corporation | Method and system for managing data and users of data in a data processing system |
US5584039A (en) * | 1993-11-08 | 1996-12-10 | International Business Machines Corporation | System for coordinating execution of multiple concurrent channel programs without host processor involvement using suspend and resume commands to control data transfer between I/O devices |
JP3528094B2 (en) * | 1994-02-09 | 2004-05-17 | 株式会社日立製作所 | Bus utilization method and storage control device |
US6769009B1 (en) | 1994-05-31 | 2004-07-27 | Richard R. Reisman | Method and system for selecting a personalized set of information channels |
US5907684A (en) * | 1994-06-17 | 1999-05-25 | International Business Machines Corporation | Independent channel coupled to be shared by multiple physical processing nodes with each node characterized as having its own memory, CPU and operating system image |
US5548791A (en) * | 1994-07-25 | 1996-08-20 | International Business Machines Corporation | Input/output control system with plural channel paths to I/O devices |
US5860022A (en) * | 1994-07-26 | 1999-01-12 | Hitachi, Ltd. | Computer system and method of issuing input/output commands therefrom |
EP0712220A1 (en) * | 1994-11-08 | 1996-05-15 | International Business Machines Corporation | Hop-by-hop flow control in an ATM network |
US5564040A (en) * | 1994-11-08 | 1996-10-08 | International Business Machines Corporation | Method and apparatus for providing a server function in a logically partitioned hardware machine |
US5613163A (en) * | 1994-11-18 | 1997-03-18 | International Business Machines Corporation | Method and system for predefined suspension and resumption control over I/O programs |
US5671441A (en) * | 1994-11-29 | 1997-09-23 | International Business Machines Corporation | Method and apparatus for automatic generation of I/O configuration descriptions |
US5600793A (en) * | 1994-12-20 | 1997-02-04 | International Business Machines Corporation | Method and system of bi-directional parallel port data transfer between data processing systems |
US5680580A (en) * | 1995-02-28 | 1997-10-21 | International Business Machines Corporation | Remote copy system for setting request interconnect bit in each adapter within storage controller and initiating request connect frame in response to the setting bit |
TW388982B (en) * | 1995-03-31 | 2000-05-01 | Samsung Electronics Co Ltd | Memory controller which executes read and write commands out of order |
US5742845A (en) * | 1995-06-22 | 1998-04-21 | Datascape, Inc. | System for extending present open network communication protocols to communicate with non-standard I/O devices directly coupled to an open network |
JP3225804B2 (en) * | 1995-09-05 | 2001-11-05 | 株式会社日立製作所 | I / O channel expansion method |
US5996026A (en) * | 1995-09-05 | 1999-11-30 | Hitachi, Ltd. | Method and apparatus for connecting i/o channels between sub-channels and devices through virtual machines controlled by a hypervisor using ID and configuration information |
US6125411A (en) * | 1995-09-13 | 2000-09-26 | Hitachi, Ltd. | System storing plural I/O arrangement information wherein each I/O arrangement information corresponding to each operating system is created in response to more than two operating systems |
GB2291990A (en) | 1995-09-27 | 1996-02-07 | Memory Corp Plc | Flash-memory management system |
US5831985A (en) * | 1995-11-09 | 1998-11-03 | Emc Corporation | Method and apparatus for controlling concurrent data transmission from multiple sources in a channel communication system |
US5793983A (en) * | 1996-01-22 | 1998-08-11 | International Business Machines Corp. | Input/output channel interface which automatically deallocates failed subchannel and re-segments data block for transmitting over a reassigned subchannel |
US5812877A (en) * | 1996-03-15 | 1998-09-22 | Adaptec, Inc. | I/O command block chain structure in a memory |
US5894583A (en) * | 1996-04-09 | 1999-04-13 | International Business Machines Corporation | Variable timeout method for improving missing-interrupt-handler operations in an environment having I/O devices shared by one or more systems |
US5768620A (en) * | 1996-04-09 | 1998-06-16 | International Business Machines Corporation | Variable timeout method in a missing-interrupt-handler for I/O requests issued by the same operating system |
US5758190A (en) * | 1996-04-09 | 1998-05-26 | International Business Machines Corporation | Control unit threshold timeout controls for software missing interrupt handlers in operating systems |
US5901327A (en) * | 1996-05-28 | 1999-05-04 | Emc Corporation | Bundling of write data from channel commands in a command chain for transmission over a data link between data storage systems for remote data mirroring |
US6108655A (en) * | 1996-07-19 | 2000-08-22 | Cisco Technology, Inc. | Method and apparatus for transmitting images and other objects over a computer network system |
SG74611A1 (en) * | 1997-02-14 | 2000-08-22 | Canon Kk | Data communication apparatus and method |
JP3697831B2 (en) | 1997-04-18 | 2005-09-21 | 株式会社日立製作所 | Computer system |
TW375529B (en) * | 1997-05-14 | 1999-12-01 | Sega Corp | Data transmission method and game system using the same |
US5918028A (en) * | 1997-07-08 | 1999-06-29 | Motorola, Inc. | Apparatus and method for smart host bus adapter for personal computer cards |
US6263380B1 (en) * | 1997-10-14 | 2001-07-17 | Mitutoyo Corporation | Measurement data processing unit |
US6070070A (en) | 1998-01-20 | 2000-05-30 | Aeris.Net | Method and apparatus for remote telephony switch control |
US6654954B1 (en) | 1998-02-17 | 2003-11-25 | International Business Machines Corporation | Computer system, program product and method utilizing executable file with alternate program code attached as a file attribute |
US6460087B1 (en) * | 1998-02-25 | 2002-10-01 | Kdd Corporation | Method of transferring file |
US6128311A (en) | 1998-02-26 | 2000-10-03 | 3Com Corporation | Method and system for interfacing parallelly interfaced devices through a serial bus |
US6360282B1 (en) | 1998-03-25 | 2002-03-19 | Network Appliance, Inc. | Protected control of devices by user applications in multiprogramming environments |
US6353612B1 (en) * | 1998-06-19 | 2002-03-05 | Brocade Communications Systems, Inc. | Probing device |
US6693880B2 (en) * | 1998-09-10 | 2004-02-17 | International Business Machines Corporation | System of controlling the flow of information between senders and receivers across links being used as channels |
US6202095B1 (en) * | 1998-10-07 | 2001-03-13 | International Business Machines Corporation | Defining characteristics between processing systems |
US6230218B1 (en) * | 1998-10-14 | 2001-05-08 | International Business Machines Corporation | Apparatus for transferring execution of certain channel functions to a control unit and having means for combining certain commands and data packets in one sequence |
US6185631B1 (en) * | 1998-10-14 | 2001-02-06 | International Business Machines Corporation | Program for transferring execution of certain channel functions to a control unit and having means for combining certain commands and data packets in one sequence |
US6343335B1 (en) * | 1998-10-29 | 2002-01-29 | International Business Machines Corporation | System for repositioning an I/O device to a predetermined position to retry a program without knowledge of which part of the program caused the retry |
US6195330B1 (en) * | 1998-11-05 | 2001-02-27 | David C. Sawey | Method and system for hit-less switching |
KR100273641B1 (en) * | 1998-11-11 | 2000-12-15 | 윤종용 | Apparatus and method for processing group cell in shared memory |
JP3990833B2 (en) * | 1998-12-11 | 2007-10-17 | キヤノン株式会社 | Communication control method and apparatus |
US6347334B1 (en) * | 1999-01-06 | 2002-02-12 | Mcdata Corporation | Self-description extended link service for networks |
US6772207B1 (en) * | 1999-01-28 | 2004-08-03 | Brocade Communications Systems, Inc. | System and method for managing fibre channel switching devices |
US6351779B1 (en) * | 1999-03-12 | 2002-02-26 | Agilent Technologies, Inc. | Extension library to standard visa library for support of complex I/O functions |
US6484217B1 (en) * | 1999-04-20 | 2002-11-19 | International Business Machines Corporation | Managing shared devices in a data processing system |
US6738647B1 (en) | 1999-04-23 | 2004-05-18 | Numerex Corporation | Method and system for expanding the data payload of data messages transported via a cellular network control channel |
US6401223B1 (en) * | 1999-05-21 | 2002-06-04 | Unisys Corporation | Programmable system for invalidating pending requests within a data processing system |
TW549004B (en) * | 1999-06-15 | 2003-08-21 | Matsushita Electric Works Ltd | Portable programming device for supervisory remote control system |
US6718139B1 (en) * | 1999-09-13 | 2004-04-06 | Ciena Corporation | Optical fiber ring communication system |
US6609165B1 (en) | 1999-09-27 | 2003-08-19 | International Business Machines Corporation | Method and apparatus for using fibre channel extended link service commands in a point-to-point configuration |
US6651125B2 (en) * | 1999-09-28 | 2003-11-18 | International Business Machines Corporation | Processing channel subsystem pending I/O work queues based on priorities |
US7046665B1 (en) | 1999-10-26 | 2006-05-16 | Extreme Networks, Inc. | Provisional IP-aware virtual paths over networks |
JP2001134523A (en) * | 1999-11-09 | 2001-05-18 | Hitachi Ltd | Channel device, its control method, and computer- readable recording medium stored with channel control program |
US6718419B1 (en) | 1999-11-17 | 2004-04-06 | Globespanvirata, Inc. | System and method for extending the number of addressable physical devices on a data bus |
US6922548B1 (en) | 2000-04-24 | 2005-07-26 | Microsoft Corporation | Providing remote network driver interface specification services over a wireless radio-frequency medium |
US6584511B1 (en) | 2000-03-24 | 2003-06-24 | Unisys Corporation | Loop initialization procedure exception handling for fibre channel transmissions |
US6963940B1 (en) | 2000-03-30 | 2005-11-08 | International Business Machines Corporation | Measuring utilization of individual components of channels |
US6877043B2 (en) | 2000-04-07 | 2005-04-05 | Broadcom Corporation | Method for distributing sets of collision resolution parameters in a frame-based communications network |
US6658603B1 (en) * | 2000-04-17 | 2003-12-02 | International Business Machines Corporation | Method and apparatus for efficiently generating and implementing engine error codes and verifying the correctness of the implementation of the engine error codes |
US6594785B1 (en) | 2000-04-28 | 2003-07-15 | Unisys Corporation | System and method for fault handling and recovery in a multi-processing system having hardware resources shared between multiple partitions |
US6862322B1 (en) * | 2000-05-19 | 2005-03-01 | International Business Machines Corporation | Switchable-bandwidth optical receiver |
US6609161B1 (en) * | 2000-06-01 | 2003-08-19 | Adaptec, Inc. | Two-dimensional execution queue for host adapters |
US7142520B1 (en) | 2000-06-16 | 2006-11-28 | Nokia Mobile Phones Ltd. | Method and apparatus for mobile internet protocol regional paging |
JP2002016655A (en) * | 2000-06-28 | 2002-01-18 | Sony Corp | Transmission method, transmission system, transmitter and transmission controller |
US6662319B1 (en) * | 2000-08-31 | 2003-12-09 | Hewlett-Packard Development Company, L.P. | Special encoding of known bad data |
ATE546018T1 (en) | 2000-08-31 | 2012-03-15 | Dolby Lab Licensing Corp | METHOD AND ARRANGEMENT FOR AUDIO MATRIX DECODING |
US6694390B1 (en) * | 2000-09-11 | 2004-02-17 | Intel Corporation | Managing bus transaction dependencies |
US7292597B2 (en) | 2000-09-28 | 2007-11-06 | Teridian Semiconductor Corp. | Method and apparatus for transparent implementation of link-suspend capabilities in network devices |
US6751683B1 (en) | 2000-09-29 | 2004-06-15 | International Business Machines Corporation | Method, system and program products for projecting the impact of configuration changes on controllers |
US6678748B2 (en) | 2000-09-29 | 2004-01-13 | Emc Corporation | Method for optimizing multiple input/output requests to a single logical device |
US6950888B1 (en) | 2000-09-29 | 2005-09-27 | International Business Machines Corporation | Method, system and program products for determining whether I/O constraints exist for controllers of a computing environment |
US6594712B1 (en) | 2000-10-20 | 2003-07-15 | Banderacom, Inc. | Inifiniband channel adapter for performing direct DMA between PCI bus and inifiniband link |
US6697983B1 (en) * | 2000-10-24 | 2004-02-24 | At&T Wireless Services, Inc. | Data link layer tunneling technique for high-speed data in a noisy wireless environment |
US6622268B2 (en) * | 2000-11-29 | 2003-09-16 | Intel Corp | Method and apparatus for propagating error status over an ECC protected channel |
US7127514B2 (en) * | 2000-12-28 | 2006-10-24 | Microsoft Corporation | Stateless distributed computer architecture with server-oriented state-caching objects maintained on network or client |
US7155569B2 (en) * | 2001-02-28 | 2006-12-26 | Lsi Logic Corporation | Method for raid striped I/O request generation using a shared scatter gather list |
US6834363B2 (en) * | 2001-03-22 | 2004-12-21 | International Business Machines Corporation | Method for prioritizing bus errors |
US6898202B2 (en) * | 2001-06-27 | 2005-05-24 | International Business Machines Corporation | Method, apparatus and computer program for informing a requesting device of port configuration changes in a computer network switching device |
US20030056000A1 (en) * | 2001-07-26 | 2003-03-20 | Nishan Systems, Inc. | Transfer ready frame reordering |
US6910149B2 (en) | 2001-09-24 | 2005-06-21 | Intel Corporation | Multi-device link aggregation |
US7315911B2 (en) | 2005-01-20 | 2008-01-01 | Dot Hill Systems Corporation | Method for efficient inter-processor communication in an active-active RAID system using PCI-express links |
US6754738B2 (en) * | 2001-09-28 | 2004-06-22 | International Business Machines Corporation | Low overhead I/O interrupt |
US6859866B2 (en) * | 2001-10-01 | 2005-02-22 | International Business Machines Corporation | Synchronizing processing of commands invoked against duplexed coupling facility structures |
US6745299B2 (en) * | 2001-11-19 | 2004-06-01 | Hewlett-Packard Development Company, L.P. | Method for evaluation of scalable symmetric multiple processor cache coherency protocols and algorithms |
US7512133B2 (en) | 2001-12-03 | 2009-03-31 | International Business Machines Corporation | Method and apparatus for obtaining multiple port addresses by a fibre channel from a network fabric |
US7599360B2 (en) | 2001-12-26 | 2009-10-06 | Cisco Technology, Inc. | Methods and apparatus for encapsulating a frame for transmission in a storage area network |
US7085860B2 (en) | 2002-01-11 | 2006-08-01 | International Business Machines Corporation | Method and apparatus for a non-disruptive recovery of a single partition in a multipartitioned data processing system |
US7007142B2 (en) * | 2002-02-19 | 2006-02-28 | Intel Corporation | Network data storage-related operations |
US7099814B2 (en) | 2002-03-29 | 2006-08-29 | International Business Machines Corportion | I/O velocity projection for bridge attached channel |
US6898723B2 (en) * | 2002-04-01 | 2005-05-24 | Mitac International Corp. | Method for verifying clock signal frequency of computer sound interface that involves checking whether count value of counter is within tolerable count range |
US7543087B2 (en) | 2002-04-22 | 2009-06-02 | Alacritech, Inc. | Freeing transmit memory on a network interface device prior to receiving an acknowledgement that transmit data has been received by a remote device |
JP4704659B2 (en) | 2002-04-26 | 2011-06-15 | 株式会社日立製作所 | Storage system control method and storage control device |
US20030208581A1 (en) | 2002-05-02 | 2003-11-06 | Behren Paul D. Von | Discovery of fabric devices using information from devices and switches |
US7660421B2 (en) | 2002-06-28 | 2010-02-09 | Hewlett-Packard Development Company, L.P. | Method and system for secure storage, transmission and control of cryptographic keys |
US7120728B2 (en) | 2002-07-31 | 2006-10-10 | Brocade Communications Systems, Inc. | Hardware-based translating virtualization switch |
US7107385B2 (en) | 2002-08-09 | 2006-09-12 | Network Appliance, Inc. | Storage virtualization by layering virtual disk objects on a file system |
US6826661B2 (en) * | 2002-08-30 | 2004-11-30 | Veritas Operating Corporation | Methods and systems for storage architectures |
US20040054776A1 (en) * | 2002-09-16 | 2004-03-18 | Finisar Corporation | Network expert analysis process |
US7539777B1 (en) * | 2002-10-25 | 2009-05-26 | Cisco Technology, Inc. | Method and system for network time protocol forwarding |
US7080094B2 (en) * | 2002-10-29 | 2006-07-18 | Lockheed Martin Corporation | Hardware accelerated validating parser |
US7061485B2 (en) * | 2002-10-31 | 2006-06-13 | Hewlett-Packard Development Company, Lp. | Method and system for producing a model from optical images |
US7202801B2 (en) * | 2002-12-11 | 2007-04-10 | Geospatial Technologies, Inc. | Method and apparatus for an automated location-based, dynamic notification system (ALDNS) |
US7277387B2 (en) * | 2003-01-30 | 2007-10-02 | Wind River Systems, Inc. | Package manager |
US7324455B2 (en) * | 2003-03-14 | 2008-01-29 | International Business Machines Corporation | Transfer of error-analysis and statistical data in a fibre channel input/output system |
US6915378B2 (en) * | 2003-04-23 | 2005-07-05 | Hypernova Technologies, Inc. | Method and system for improving the performance of a processing system |
US7000036B2 (en) | 2003-05-12 | 2006-02-14 | International Business Machines Corporation | Extended input/output measurement facilities |
US7085898B2 (en) * | 2003-05-12 | 2006-08-01 | International Business Machines Corporation | Coherency management for a “switchless” distributed shared memory computer system |
US7058735B2 (en) | 2003-06-02 | 2006-06-06 | Emulex Design & Manufacturing Corporation | Method and apparatus for local and distributed data memory access (“DMA”) control |
US7266296B2 (en) | 2003-06-11 | 2007-09-04 | Intel Corporation | Architecture and method for framing control and data bursts over 10 Gbit Ethernet with and without WAN interface sublayer support |
TWI271626B (en) * | 2003-06-17 | 2007-01-21 | Delta Electronics Inc | Data transmission method for microprocessors of programmable logic controller |
US7684401B2 (en) * | 2003-07-21 | 2010-03-23 | Qlogic, Corporation | Method and system for using extended fabric features with fibre channel switch elements |
US7124207B1 (en) * | 2003-08-14 | 2006-10-17 | Adaptec, Inc. | I2O command and status batching |
US7149823B2 (en) | 2003-08-29 | 2006-12-12 | Emulex Corporation | System and method for direct memory access from host without processor intervention wherein automatic access to memory during host start up does not occur |
KR100829471B1 (en) * | 2003-10-17 | 2008-05-19 | 니폰덴신뎅와 가부시키가이샤 | Mail distribution system, mail distribution method, and mail distribution program |
KR20050043426A (en) * | 2003-11-06 | 2005-05-11 | 삼성전자주식회사 | Command transmitting method and apparatus in the pipeline bus system |
US20050105456A1 (en) * | 2003-11-18 | 2005-05-19 | Cookson Christopher J. | Double-sided optical disc |
US7581033B2 (en) | 2003-12-05 | 2009-08-25 | Unisys Corporation | Intelligent network interface card (NIC) optimizations |
US7634582B2 (en) * | 2003-12-19 | 2009-12-15 | Intel Corporation | Method and architecture for optical networking between server and storage area networks |
US7564791B2 (en) | 2003-12-29 | 2009-07-21 | Intel Corporation | Monitoring packet flows |
US7382733B2 (en) | 2004-02-12 | 2008-06-03 | International Business Machines Corporation | Method for handling reordered data packets |
US7295897B2 (en) * | 2004-02-23 | 2007-11-13 | Standard Microsystems Corporation | Mapping a plurality of sensors to respective zones in a fan control system |
US7133988B2 (en) | 2004-02-25 | 2006-11-07 | Hitachi, Ltd. | Method and apparatus for managing direct I/O to storage systems in virtualization |
TWI369616B (en) | 2004-02-27 | 2012-08-01 | Eplus Capital Inc | System and method for user creation and direction of a rich-content life-cycle |
US20050223291A1 (en) * | 2004-03-24 | 2005-10-06 | Zimmer Vincent J | Methods and apparatus to provide an execution mode transition |
JP2005293363A (en) | 2004-04-01 | 2005-10-20 | Toshiba Corp | Disk array controller and information processing device |
US8171170B2 (en) * | 2004-04-30 | 2012-05-01 | Emc Corporation | Storage switch task processing synchronization |
US7240273B2 (en) * | 2004-05-13 | 2007-07-03 | Industrial Technology Research Institute | Cyclic redundancy check modification for message length detection and error detection |
US7555554B2 (en) | 2004-08-06 | 2009-06-30 | Microsoft Corporation | System and method for generating selectable extension to media transport protocol |
US7711871B1 (en) | 2004-08-30 | 2010-05-04 | Crossroads Systems, Inc. | Interface device and method for command processing |
US7443798B2 (en) * | 2004-09-03 | 2008-10-28 | Agere Systems Inc. | Transmit adaptive equalization for communication system with one or more serial data channels |
US7577772B2 (en) | 2004-09-08 | 2009-08-18 | Qlogic, Corporation | Method and system for optimizing DMA channel selection |
GB2419198A (en) * | 2004-10-14 | 2006-04-19 | Hewlett Packard Development Co | Identifying performance affecting causes in a data storage system |
US7398335B2 (en) | 2004-11-22 | 2008-07-08 | Qlogic, Corporation | Method and system for DMA optimization in host bus adapters |
JP4575119B2 (en) | 2004-11-25 | 2010-11-04 | 株式会社日立製作所 | Storage system |
US7164425B2 (en) | 2004-12-21 | 2007-01-16 | Qlogic Corporation | Method and system for high speed network application |
US7672323B2 (en) * | 2005-01-14 | 2010-03-02 | Cisco Technology, Inc. | Dynamic and intelligent buffer management for SAN extension |
US7526633B2 (en) | 2005-03-23 | 2009-04-28 | Qualcomm Incorporated | Method and system for encoding variable length packets with variable instruction sizes |
JP2006277583A (en) * | 2005-03-30 | 2006-10-12 | Hitachi Ltd | Data processing system, data processing method and program |
EP2582158B1 (en) | 2005-06-05 | 2016-08-10 | Starkey Laboratories, Inc. | Communication system for wireless audio devices |
US7970953B2 (en) | 2005-06-30 | 2011-06-28 | Intel Corporation | Serial ATA port addressing |
US7797463B2 (en) | 2005-06-30 | 2010-09-14 | Intel Corporation | Hardware assisted receive channel frame handling via data offset comparison in SAS SSP wide port applications |
JP2007058646A (en) * | 2005-08-25 | 2007-03-08 | Hitachi Ltd | Data processing system |
US20070072543A1 (en) * | 2005-09-06 | 2007-03-29 | Nokia Corporation | Enhanced signaling of pre-configured interaction message in service guide |
US7577773B1 (en) | 2005-09-09 | 2009-08-18 | Qlogic, Corporation | Method and system for DMA optimization |
JP4527640B2 (en) * | 2005-09-15 | 2010-08-18 | 株式会社ソニー・コンピュータエンタテインメント | Data reading device |
JP2007122108A (en) | 2005-10-25 | 2007-05-17 | Hitachi Ltd | Control of storage system using disk drive device with self-check function |
US7484021B2 (en) | 2005-10-27 | 2009-01-27 | Cisco Technology, Inc. | Technique for implementing virtual fabric membership assignments for devices in a storage area network |
US20070162631A1 (en) | 2005-12-28 | 2007-07-12 | International Business Machines Corporation | Method for selectable software-hardware internet SCSI |
US7594057B1 (en) | 2006-01-09 | 2009-09-22 | Qlogic, Corporation | Method and system for processing DMA requests |
JP2007199975A (en) * | 2006-01-26 | 2007-08-09 | Hitachi Ltd | Data-processing system and data-processing method |
US9032164B2 (en) * | 2006-02-17 | 2015-05-12 | Emulex Corporation | Apparatus for performing storage virtualization |
US7743197B2 (en) | 2006-05-11 | 2010-06-22 | Emulex Design & Manufacturing Corporation | System and method for virtualizing PCIe devices |
US20080040519A1 (en) * | 2006-05-02 | 2008-02-14 | Alacritech, Inc. | Network interface device with 10 Gb/s full-duplex transfer rate |
US8381214B2 (en) * | 2006-05-05 | 2013-02-19 | Microsoft Corporation | Extensible job submission |
US7630405B1 (en) | 2006-05-27 | 2009-12-08 | Cisco Technology, Inc. | Techniques for ensuring synchronized processing at remote fiber channel and fiber connectivity networks |
US7826349B2 (en) | 2006-05-30 | 2010-11-02 | Intel Corporation | Connection management mechanism |
US20080043563A1 (en) | 2006-08-15 | 2008-02-21 | International Business Machines Corporation | Flexibly controlling the transfer of data between input/output devices and memory |
US7500030B2 (en) | 2006-08-30 | 2009-03-03 | International Business Machines Corporation | Control of information units in fibre channel communications |
US8032581B2 (en) | 2006-08-30 | 2011-10-04 | International Business Machines Corporation | Persistent information unit pacing |
US7502873B2 (en) | 2006-10-10 | 2009-03-10 | International Business Machines Corporation | Facilitating access to status and measurement data associated with input/output processing |
US7500023B2 (en) | 2006-10-10 | 2009-03-03 | International Business Machines Corporation | Facilitating input/output processing by using transport control words to reduce input/output communications |
US7668984B2 (en) | 2007-01-10 | 2010-02-23 | International Business Machines Corporation | Low latency send queues in I/O adapter hardware |
US7797414B2 (en) | 2007-01-31 | 2010-09-14 | International Business Machines Corporation | Establishing a logical path between servers in a coordinated timing network |
US8942219B2 (en) * | 2007-04-13 | 2015-01-27 | Hart Communication Foundation | Support for network management and device communications in a wireless network |
US7765336B2 (en) | 2007-06-11 | 2010-07-27 | Emulex Design & Manufacturing Corporation | Autonomous mapping of protected data streams to fibre channel frames |
US7631128B1 (en) | 2007-06-28 | 2009-12-08 | Emc Corporation | Protocol controller for a data storage system |
US8020074B2 (en) | 2007-08-24 | 2011-09-13 | Datadirect Networks, Inc. | Method for auto-correction of errors in a RAID memory system |
US8254571B1 (en) | 2007-12-21 | 2012-08-28 | Voltage Security, Inc. | Cryptographic system with halting key derivation function capabilities |
JP2009184260A (en) | 2008-02-07 | 2009-08-20 | Kyocera Mita Corp | Image forming apparatus |
US7917813B2 (en) | 2008-02-14 | 2011-03-29 | International Business Machines Corporation | Exception condition determination at a control unit in an I/O processing system |
US8082481B2 (en) | 2008-02-14 | 2011-12-20 | International Business Machines Corporation | Multiple CRC insertion in an output data stream |
US9052837B2 (en) | 2008-02-14 | 2015-06-09 | International Business Machines Corporation | Processing communication data in a ships passing condition |
US7840717B2 (en) | 2008-02-14 | 2010-11-23 | International Business Machines Corporation | Processing a variable length device command word at a control unit in an I/O processing system |
US8176222B2 (en) | 2008-02-14 | 2012-05-08 | International Business Machines Corporation | Early termination of an I/O operation in an I/O processing system |
US7937507B2 (en) | 2008-02-14 | 2011-05-03 | International Business Machines Corporation | Extended measurement word determination at a channel subsystem of an I/O processing system |
US8478915B2 (en) | 2008-02-14 | 2013-07-02 | International Business Machines Corporation | Determining extended capability of a channel path |
US8196149B2 (en) | 2008-02-14 | 2012-06-05 | International Business Machines Corporation | Processing of data to determine compatability in an input/output processing system |
US7840718B2 (en) | 2008-02-14 | 2010-11-23 | International Business Machines Corporation | Processing of data to suspend operations in an input/output processing log-out system |
US7908403B2 (en) | 2008-02-14 | 2011-03-15 | International Business Machines Corporation | Reserved device access contention reduction |
US8214562B2 (en) | 2008-02-14 | 2012-07-03 | International Business Machines Corporation | Processing of data to perform system changes in an input/output processing system |
US8001298B2 (en) | 2008-02-14 | 2011-08-16 | International Business Machines Corporation | Providing extended measurement data in an I/O processing system |
US7899944B2 (en) | 2008-02-14 | 2011-03-01 | International Business Machines Corporation | Open exchange limiting in an I/O processing system |
US7941570B2 (en) | 2008-02-14 | 2011-05-10 | International Business Machines Corporation | Bi-directional data transfer within a single I/O operation |
US8312189B2 (en) | 2008-02-14 | 2012-11-13 | International Business Machines Corporation | Processing of data to monitor input/output operations |
US8117347B2 (en) | 2008-02-14 | 2012-02-14 | International Business Machines Corporation | Providing indirect data addressing for a control block at a channel subsystem of an I/O processing system |
US8108570B2 (en) | 2008-02-14 | 2012-01-31 | International Business Machines Corporation | Determining the state of an I/O operation |
US8166206B2 (en) | 2008-02-14 | 2012-04-24 | International Business Machines Corporation | Cancel instruction and command for determining the state of an I/O operation |
US7904605B2 (en) | 2008-02-14 | 2011-03-08 | International Business Machines Corporation | Computer command and response for determining the state of an I/O operation |
US7890668B2 (en) | 2008-02-14 | 2011-02-15 | International Business Machines Corporation | Providing indirect data addressing in an input/output processing system where the indirect data address list is non-contiguous |
US8095847B2 (en) | 2008-02-14 | 2012-01-10 | International Business Machines Corporation | Exception condition handling at a channel subsystem in an I/O processing system |
GB2460841B (en) | 2008-06-10 | 2012-01-11 | Virtensys Ltd | Methods of providing access to I/O devices |
US7983257B2 (en) | 2008-07-18 | 2011-07-19 | Emulex Design & Manufacturing Corporation | Hardware switch for hypervisors and blade servers |
US7937504B2 (en) | 2008-07-31 | 2011-05-03 | International Business Machines Corporation | Transport control channel program message pairing |
US8055807B2 (en) | 2008-07-31 | 2011-11-08 | International Business Machines Corporation | Transport control channel program chain linking including determining sequence order |
US20100064072A1 (en) | 2008-09-09 | 2010-03-11 | Emulex Design & Manufacturing Corporation | Dynamically Adjustable Arbitration Scheme |
JP5107880B2 (en) | 2008-12-10 | 2012-12-26 | 株式会社日立製作所 | Data transfer processing apparatus and method |
CN101551736B (en) * | 2009-05-20 | 2010-11-03 | 杭州华三通信技术有限公司 | Cache management device and method based on address pointer linked list |
US8332542B2 (en) | 2009-11-12 | 2012-12-11 | International Business Machines Corporation | Communication with input/output system devices |
US8914812B2 (en) | 2010-01-08 | 2014-12-16 | International Business Machines Corporation | Controlling operations according to another system's architecture |
US8732357B2 (en) | 2010-10-28 | 2014-05-20 | International Business Machines Corporation | Apparatus and method for dynamically enabling and disabling write XFR—RDY |
US8583988B2 (en) | 2011-06-01 | 2013-11-12 | International Business Machines Corporation | Fibre channel input/output data routing system and method |
-
2008
- 2008-02-14 US US12/031,038 patent/US7890668B2/en active Active
-
2009
- 2009-02-10 JP JP2010546308A patent/JP5181141B2/en active Active
- 2009-02-10 RU RU2010137636/08A patent/RU2505851C2/en active
- 2009-02-10 DE DE602009000463T patent/DE602009000463D1/en active Active
- 2009-02-10 CA CA2704138A patent/CA2704138C/en active Active
- 2009-02-10 DK DK09709555.8T patent/DK2176771T3/en active
- 2009-02-10 KR KR1020107016961A patent/KR101174997B1/en active IP Right Grant
- 2009-02-10 PL PL09709555T patent/PL2176771T3/en unknown
- 2009-02-10 CN CN2009801052284A patent/CN101946242B/en active Active
- 2009-02-10 EP EP09709555A patent/EP2176771B1/en active Active
- 2009-02-10 ES ES09709555T patent/ES2358314T3/en active Active
- 2009-02-10 AT AT09709555T patent/ATE492847T1/en active
- 2009-02-10 SI SI200930016T patent/SI2176771T1/en unknown
- 2009-02-10 PT PT09709555T patent/PT2176771E/en unknown
- 2009-02-10 BR BRPI0908825-3A patent/BRPI0908825B1/en active IP Right Grant
- 2009-02-10 WO PCT/EP2009/051485 patent/WO2009101067A2/en active Application Filing
-
2010
- 2010-07-21 IL IL207119A patent/IL207119A/en active IP Right Grant
-
2011
- 2011-01-24 CY CY20111100072T patent/CY1111135T1/en unknown
- 2011-02-10 US US13/024,468 patent/US8392619B2/en active Active
-
2013
- 2013-03-04 US US13/784,132 patent/US9043494B2/en active Active
-
2014
- 2014-09-11 US US14/483,700 patent/US9436272B2/en active Active
-
2016
- 2016-08-04 US US15/228,436 patent/US9720844B2/en active Active
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9720844B2 (en) | Providing indirect data addressing in an input/output processing system where the indirect data address list is non-contiguous | |
CA2704133C (en) | Bi-directional data transfer within a single i/o operation | |
US7840717B2 (en) | Processing a variable length device command word at a control unit in an I/O processing system | |
US9292224B2 (en) | Providing indirect data addressing for a control block at a channel subsystem of an I/O processing system | |
US8082481B2 (en) | Multiple CRC insertion in an output data stream | |
JP2011512591A5 (en) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request |
Effective date: 20131127 |