US10671318B2

US10671318B2 - Processing a chain of a plurality of write requests

Info

Publication number: US10671318B2
Application number: US16/005,591
Authority: US
Inventors: Jeffrey A. Berger; Susan K. Candelaria; Matthew J. Kalos; Beth A. Peterson; Harry M. Yudenfriend
Original assignee: International Business Machines Corp
Current assignee: International Business Machines Corp
Priority date: 2016-05-10
Filing date: 2018-06-11
Publication date: 2020-06-02
Also published as: US20180293027A1; US10067717B2; US20170329557A1

Abstract

Provided are a computer program product, system, and method for processing a chain of a plurality of write requests including a commit wait flag and plurality of write requests, wherein each write request group includes write transactions directed to the storage. A determination is made as to whether the commit wait flag has a first value or a second value. The write requests are processed by requiring a current write request comprising one of the write requests being processed to complete before beginning to write data for a next write request following the current write request in the write request chain in response to the commit wait flag having the first value. The write requests are processed by processing the next write request before completing the current write request in response to the commit wait flag having the second value.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to a computer program product, system, and method for processing a chain of a plurality of write requests.

2. Description of the Related Art

Write operations may be grouped in a chain of write requests, such as the case with a zHPF Channel Program. The zHPF Channel Program will include a Transport Control Area (TCA) containing the commands and control parameters. Each command is represented by a Device Command Word (DCW) that consists of a command code, flags to indicate chaining and other options, a control data count, and a data byte count, if the command is used to transfer data. If the command transfers control data (command parameters) to the device, the control data follows the DCW in the TCA. The command code used is the same as those used in a Channel Command Word (CCW).

The CCW is the original I/O operation used for communications with the channel subsystem between a host server, e.g., mainframe, and a channel attached storage system (channel attached device). The CCW contains a channel command, such as read, write, or control, along with the data address of the data area involved. The data is passed to the channel subsystem. The channel subsystem communicates status of the I/O back to the issuing application.

Unlike CCWs, DCWs do not point to their corresponding I/O buffers. The I/O buffers for all DCWs are pointed to by the TCW, and the I/O buffers associated with a particular DCW are based on the amount of data transferred by the previous DCWs.

A Fibre Connection (“FICON”) (Command Mode) write chain would consist of a number of CCWs which would allow the host server to transfer data to the attached storage system. Each CCW contains a command to be executed and either points to control parameters, or points to storage areas containing the data to be read or written. A CCW may point directly to the storage areas or may use some format of indirect addressing (Indirect Address List (IDAL) or a Modified Indirect Address List (MIDAL)) to point to the storage areas. A standard FICON write chain may consist of a Define Extent, Locate Record (Extended), and Write Commands. The Define Extent and Locate Record (Extended) may be collapsed into the Prefix Command. The Locate Record parameters describe a domain of operations that will immediately follow in the chain. These parameters define the read or write domain type, the starting address for the data transfer, as well as the expected number of data transfer commands in the chain. The chain may also include additional Locate Record (Extended) commands after the initial domain of write commands have been completed. These additional Locate Record (Extended) commands are called Imbedded Locate Record commands and allow for additional domains to be defined in the chain. These domains may be contiguous or discontiguous.

A System Z High Performance FICON (“zHPF”) (Transport Mode) write chain is a further step in the compression of the control data used to describe the transfer operations performed by the chain. A write DCW will specify a PFX command with an Imbedded CCW opcode and Intent Count. The Imbedded CCW opcode would be equivalent to the Write Command Codes that are used for the Write CCWs that follow the DX/LR or PFX in a FICON write chain. In addition, the Prefix may also have an Imbedded Locate Record count and an Imbedded Locate Record List. These Imbedded Locate Records entries allow for additional domains to be specified in a single DCW. In addition, there may be additional Locate Record Extended DCWs in the Transport Mode chain which may also have Imbedded Locate Record entries.

There is a need in the art for improved techniques for processing a write chain of write requests, such as a write chain of many locate record commands.

SUMMARY

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a storage environment.

FIG. 2 illustrates an embodiment of a write chain of write requests.

FIG. 3 illustrates an embodiment of operations to generate a write request chain.

FIG. 4 illustrates an embodiment of a reply to a write request chain.

FIG. 5 illustrates an embodiment of operations to process a received reply to a write request chain.

FIG. 6 illustrates an embodiment of operations to process a chain of write requests.

FIG. 7 illustrates a computing environment in which the components of FIG. 1 may be implemented.

DETAILED DESCRIPTION

In certain implementations, processing a write request chain of multiple groups of write requests, such as a channel command having multiple locate record (LR) domains requires that all the write requests in each group to complete before processing a next group of write requests. The storage system must stop processing and wait for the data to be committed before continuing execution in the subsequent group of writes, locate record (LR) write domain. In this way, if an I/O error occurs, which would cause the channel command to terminate, the software could select to only retry the write requests from the beginning of the write request group or LR domain that failed and not the entire chain of requests. This waiting required for all write requests to complete lowered the elapsed time of the I/O recovery after the error.

Described embodiments provide techniques to accelerate write request execution and improve I/O service times by providing a commit wait flag in the write chain allowing indication of whether a previous group of write requests, such a previous LR domain, needs to complete or commit before a next group of write requests, next LR domain, in the chain can be processed. By indicating that commit is not required, a next group of write requests in the write chain can be processed before the write data for the previous group of write requests is transferred for processing. Further, write processing will complete faster with less impact on customer performance by allowing a next group of write requests in the chain to proceed without the previous request completing. With the commit wait flag set to indicate commit is not required, the data for a next write command may be accessed and transferred before the data for the previous write command is transferred or committed.

FIG. 1 illustrates an embodiment of a mirror or single copy storage environment having a host 100, primary storage server 102 a, and secondary storage server 102 b that communicate over a network 104. The

storage servers

102 a, 102 b each include a

processor

106 a, 106 b,

system memory

108 a, 108 b, having Input/Output (I/O)

managers

110 a, 110 b that manage write requests from the host 100, and cache 112 a, 112 b, as well as a non-volatile storage device (NVS) 114 a, 114 b. Write data in the

caches

112 a, 112 b may be backed-up in the

NVS

114 a, 114 b in the

same server

102 a, 102 b, respectively. Alternatively, a

cache

112 a, 112 b in one

storage server

102 a, 102 b may backup writes in the

NVS

114 b, 114 a of the

other storage server

102 b, 102 a, respectively. A primary storage 116 a is coupled to the primary storage server 102 a and a secondary storage 116 b is coupled to the secondary storage server 102 b. The I/O managers 110 a, 110 ab manage I/O requests from the host 100 directed to data in the attached

storages

116 a, 116 b.

The host 100 includes a processor 120, a system memory 122, and an operating system 124 including includes a write request chain Application Programming Interface (API) 126 to generate write request chains of ordered write requests to process writes from applications 128 executing in the host 100 or other systems in the network 104 submitting I/O requests to the host 100.

In one embodiment, the

storage servers

102 a, 102 b include

copy services

118 a, 118 b to mirror/synchronize host 100 writes to the secondary storage sever 102 b to write to the secondary storage 116 b. In such embodiments, a host write operation does not complete and is not committed until data is confirmed to have been written to the primary 116 a and secondary 116 b storages. The I/O manager 110 a may not confirm complete to the host 100 until completing writing the data to the primary 116 a and secondary storages 116 b. Alternatively, the I/O manager 110 a may confirm complete upon storing the write data in the

cache

112 a, 112 b and/or

NVS

114 a, 114 b in the

storage servers

102 a, 102 b before the data is written to the

storage

116 a, 116 b.

In another embodiment, the server 102 a may not synchronize writes to the secondary storage server 102 b and operate as in an environment without the secondary storage server 102 b. In such case, write complete or commit indicates the write data is committed in the storage 116 a or cache 112 a and/or/NVS 114 a or 14 b.

The

storage servers

102 a and 102 b may be comprised of an enterprise storage server suitable for managing access to attached storage devices, such as the International Business Machine Corporation's (“IBM”) DS8000® storage system. (DS8000 is a registered trademark of IBM in countries throughout the world). The host 100

operating system

124 may comprise an operating system such as Z Systems Operating System (Z/OS®) from International Business Machines Corporation (“IBM”) or other operating systems known in the art. (Z/OS is a registered trademark of IBM throughout the world).

The network 104 may comprise a Storage Area Network (SAN), Local Area Network (LAN), Intranet, the Internet, Wide Area Network (WAN), peer-to-peer network, wireless network, arbitrated loop network, etc.

The

storages

116 a, 116 b may each comprise one or more storage devices, or an array of storage devices configured as Just a Bunch of Disks (JBOD), Direct Access Storage Device (DASD), Redundant Array of Independent Disks (RAID) array, virtualization device, tape storage, flash memory, etc. The storage devices comprising the

storages

116 a, 116 b may comprise hard disk drives, solid state storage device (SSD) comprised of solid state electronics, EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory, flash disk, Random Access Memory (RAM) drive, storage-class memory (SCM), etc., Phase Change Memory (PCM), resistive random access memory (RRAM), spin transfer torque memory (STM-RAM), conductive bridging RAM (CBRAM), magnetic hard disk drive, optical disk, tape, etc. Although a certain number of instances of elements, such as servers, storages, active and inactive copy relationships, etc., are shown, there may be any number of these components.

In one embodiment, the host 100

operating system

124 may include a channel subsystem, which has sub-channels that provide the information needed to access the server 102 a and underlying storage 116 a in which volumes are configured. The

storage server

102 a, 102 b I/

O managers

110 a, 110 b may include Unit Control Blocks (UCBs) that provide a software representation of the underlying volumes, and point to the sub-channel that has the information on how to access the device including the volume addressed by the UCB.

FIG. 2 illustrates an embodiment of a write request chain 200 produced by the write request chain API 126 executing in the operating system 124, or another connected host system that includes a series of

write requests

204 ₁, 204 ₂. . . 204 _nthat may specify to write data to discontiguous locations in the

storage

116 a, 116 b. The write request chain 200 includes a commit wait flag 202 indicating a commit “wait” mode where the processing of a subsequent write request 204 _i+1must wait for completion/committing of a previous write request 204 _ior a commit “no wait” mode where the processing of a subsequent write request 204 _i+1may proceed without having to wait for the previous write request 204 _ito complete, i.e., is committed. For the commit “no wait” mode, processing of a subsequent write request 204 _i+1may be initiated after initiating and beginning the transfer of data for the previous write request previous write request 204 _i, without having to wait before the transfer of the write data completes. The terms “commit” and “complete” as used herein refer to a transfer of data to the

storage

116 a, 116 b or another suitable storage, such as

cache

112 a, 112 b and/or

NVS

114 a, 114 b, such that acknowledgment can be returned that the write completed. In mirror copy environments where the data is mirrored between the primary storage server 102 a and secondary storage server 102 b, commit or complete is not confirmed until the write data is confirmed/complete at both the primary 102 a and secondary 102 b storage servers.

Each

write request

204 ₁, 204 ₂. . . 204 _nmay indicates a location in the

storage

116 a, 116 b and an operation type. In one embodiment, the each

write request

204 ₁, 204 ₂. . . 204 _nmay comprise a write request group identifying a range of storage locations, or tracks, and a series of write transactions to the identified range. In one implementation, each write request 204 _imay include a locate record (LR) domain 206 _ispecifying a range or group of tracks and a plurality of write transactions 208 _idirected to the tracks identified in the LR domain 206 _i, where the write transactions 208 _iare ordered according to a predetermined order of the tracks to which they write, i.e., ascending order. Sequential write requests 204 ₁, 204 ₂. . . 204 _nin the write request chain 200 may have write transactions to non-contiguous ranges or sections of tracks. Each locate record domain 206 _imay specify a location, search argument comprising a track and record within the track, length of data to transfer, and operation types. In further embodiments, some or all of the write requests 204 ₁, 204 ₂. . . 204 _nmay comprise a single write transaction.

In one embodiment, the write chain API 126 may generate write

requests

204 ₁, 204 ₂. . . 204 _nin a device command word (DCW), where the commit wait flag 202 is located within a prefix parameter of the DCW command word. The locate record domains 206 _iand write transactions 208 _ifor each write request group may be packaged in the prefix parameter or in parameters following the prefix parameters of the command word. In certain embodiments, the DCW chain may have a first locate record followed by embedded truncated locate records for operations to different locations.

In locate record embodiments, the host operating system 124 transfers the write requests 204 ₁, 204 ₂. . . 204 _nor locate records to a channel subsystem in the host 100 to manage the transfer of the write requests to the storage server 102 a. The channel subsystem directs the flow of read and write operations between the host 100 and storage server 102 a to relieve the host operating system 124 of the task of communicating with the storage server 102 a to allow the host operating system 124 to perform data processing and proceed concurrently with the Input/Output (I/O) processing being handled by the channel subsystem. The channel subsystem uses and manages channel paths as communication links from the host 100 to the storage server 102 a.

In one embodiment, the write request chain 200 may be used with a FICON (command mode) write chain to allow the host server to transfer data to the attached storage system. In another embodiment, the write request chain 200 may be used with a zHPF (Transport Mode) write chain. In further embodiments, the write request chain may be used with different transport and command protocols.

In FICON implementations, the write requests 204 ₁, 204 ₂. . . 204 _nor locate record domains 206 _imay be collapsed into a Prefix Command, and the locate record 206 _iparameters describe a domain of operations that will immediately follow in the chain. In zHPF implementations, a Prefix may have an imbedded locate record list, such that the imbedded locate records 206 _iallow for additional domains to be specified in a single DCW. In FICON and zHPF implementations, each

write request

204 ₁, 204 ₂. . . 204 _nincluding locate records domains 206 _ispecifies one or more write operations to perform at the storage locations, where the locate records may specify write operations for many discontiguous locations. Each locate record 206 _icommand specifies a location, search argument comprising a track and record within the track, length of data to transfer, and operation types. The locate records and the associated writes in the chain may be processed sequentially and all the write operations for one locate record domain must complete or be committed before the next locate record domain is processed.

FIG. 3 illustrates an embodiment of operations performed by the write request chain API 126 to generate a write request chain 200. Upon initiating (at block 300) an operation to generate a write request chain 200, the write request chain API 126 determines (at block 302) an order of

write requests

204 ₁, 204 ₂. . . 204 _nor locate records to include in the write request chain 200. The write request chain 200 is generated (at block 304) including a commit wait flag 202 and the plurality of

write requests

204 ₁, 204 ₂. . . 204 _ndirected to storage locations in a storage in the determined order. The write requests may comprise write request groups, each having multiple write transactions 208 _ito a specified range of tracks or locate record domain 206 _i. The write request chain API 126 may receive (at block 306) selection of a value for the commit wait flag 202, such as a first or second value, where the first value indicates a “wait” state to commit a write request 204 _ibefore initiating processing of a next write request 204 _i+1and the second value indicates “no wait”, so that a subsequent write request 204 _i+1can be processed before the previous write request 204 _iis confirmed as completed. The selection may be made by user selection through a user interface or by a program/application initiating the write. The commit wait flag 202 is set (at block 308) to the received selection of the first value (“wait”) or the second value (“no wait”). The write request chain 200 is then sent (at block 310) to the storage server 102 a to process as a standalone server or in a mirror/synchronization environment.

FIG. 4 illustrates an embodiment of a reply to a write request chain 400 from the sever 102 a I/O manager 110 a, including: a reply code 402 indicating fail or success and a last completed write request 404, which may comprise an offset into the write request chain 200 of the last completed

write request

204 ₁, 204 ₂. . . 204 _nor an address to which the last completed

write request

204 ₁, 204 ₂. . . 204 _nwas directed. Alternatively, the last completed write request 404 may not be indicated and such information may be determined or transmitted separately.

FIG. 5 illustrates an embodiment of operations performed by the host operating system 124 to process a reply from the to an initial write request chain 200 _I. Upon receiving a reply from the control unit I/O manager 104 a ₁. . . 104 a _mto the initial write request chain 200 _I, if (at block 502) complete is returned, indicating that all write

requests

204 ₁, 204 ₂. . . 204 _nwere successfully committed, then the host operating system 124 may return (at block 504) complete to the application 128 initiating the write request chain 200 _Iassociated with the reply 400. If (at block 502) a failure was returned in the reply 400, then the host operating system 124 determines (at block 506) the last completed write request 404, which may comprise an offset into the chain or the address of the write request that last completed. The host operating system 124 generates (at block 508) a recovery write request chain 200 _Rfor which the reply 400 was returned having

writes

204 _i, 204 ₂. . . 204 _nfrom the write request chain following the last completed write request 204 _i−1in the same order in which they were included in the initial write request chain 200 _I, and indicating the commit wait flag 202 as the second flag (no commit). The recovery write request chain 200 _Ris then sent (at block 510) to the storage server 102 a to continue the write chain from where the write request was interrupted.

When a reply 400 is sent to the recovery write request chain 200 _R, than the operations of FIG. 5 may be performed again with the recovery write request chain 200 _Rcomprising the write request chain being processed to generate a further recovery write request chain 200 _R+1.

For embodiments where the write request chain 200 is mirrored to a secondary storage server 102 b, then the host operating system 124 during a recovery operation may determine the last write that was committed at the secondary storage server 102 b, and generate the recovery write request chain 200 _Rto have the write request following the last completed write request at the secondary storage server 102 b if that is different from the last completed write request at the primary storage server 102 a. This difference may be determined based on a predetermined fixed difference, such that the secondary storage server 102 b is a fixed number of write requests being committed behind that of the primary storage server 102 a, or by querying the secondary storage server 102 b to determine the last committed write request for the write request chain 200.

FIG. 6 illustrates an embodiment of operations performed by the I/O manager 110 a at the primary storage server 102 a to process a write request chain 200 received from the write request chain API 126 and host 100. Upon processing (at block 600) a write request chain 200, the I/O manager 110 a determines (at block 602) whether the commit wait flag 202 indicates commit “wait” or “no wait”. If the commit wait flag 202 indicates to wait, then the I/O manager 110 a processes (at block 604) the write requests by requiring a currently processed

write request

204 ₁, 204 ₂. . . 204 _n−1to return complete or commit before processing a

next write request

204 ₂, 204 ₂. . . 204 _nin the write request chain 200. In mirror copy environments, the copy services 118 a may further wait for one

write request

204 ₁, 204 ₂. . . 204 _n−1to complete at both the primary 102 a and secondary 102 b storage servers before processing the next write request in the chain 200. The copy services 118 a would transfer a

write request

204 ₁, 204 ₂. . . 204 _n−1being processed at the primary storage server 102 a to the secondary storage server 102 b to mirror.

If (at block 602) the commit wait flag indicates “no wait”, that commit or complete does not need to occur for each write request before a next write is performed, then the then the I/O manager 110 a accesses (at block 604) a first write request 204 ₁in the write chain 200 and initiates (at block 614) the transfer of the write data for the accessed write request 204 _ito a target storage location at the

storage

116 a, 116 b indicated in the write request 200 _i, such as at the location of a locate record. If the accessed write request 204 _icomprises a write request group, then the I/O manager 110 a would process each of the write transactions 208 i for the locate record domain 206 _iof the group. In mirror/synchronization environments, upon initiating (at block 608) the processing of a write request 204 _i, the copy services 118 a would transfer the write request 204 i to the secondary storage server 102 b to process, which may be processing concurrently with previously write requests being processed at the secondary storage sever 102 b.

After initiating the write transfer, if (at block 610) there are further write requests 204 ₂. . . 204 _nthe write chain 200, then the next write request 204 ₁₊₁in the write chain 200 is accessed (at block 612). The I/O manager 110 a determines (at block 614) whether the next write request 204 ₁₊₁is directed to one or more write requests writing to tracks in a predetermined order, such as an ascending order, with respect to the tracks written in the previous write request 204 _i, previously initiated. If the tracks are not in the predetermined order, such as in a descending order, then control proceeds to block 604 where the I/O manager 110 a processes the write requests in a “wait” commit mode by requiring that the write request 204 ₁₊₁and any subsequent write requests complete processing before the next write request is processed. In an alternative embodiment, if the order is not ascending, then just the next write request 204 _i−1processed in the “wait” commit mode where it must complete before a further next write request 204 _i+2is processed. However, if the further next write request 204 _i+2is in the predetermined order with the respect to the previous write request 204 _i+1, then processing may return to “no wait” commit mode.

If (at block 614) the next write request 204 _i+1writes to tracks in the predetermined order with respect to tracks written by the previous write request 204 _i, then control proceeds back to block 608 to process that next write request 204 _i+1. This next write request may be processed and initiated before the previous write request completes.

If (at block 610) there are no further write requests to process, then if (at block 616) complete has returned for all the write requests 204 ₁, 204 ₂. . . 204 _nin the chain 200, then complete is returned (at block 618) for the write request chain 200 to the host 100. If (from the no branch of block 616) all write requests have not completed and if (at block 620) an error occurred in processing one of the write requests 204 ₁, 204 ₂. . . 204 _n, then the I/O manager 110 a generates (at block 622) a reply 400 to the write request chain 200 indicating an error, which may include the last completed write request 404. The reply 400 is returned (at block 624) to the originating host 100.

In mirror/synchronization environments, the I/O manager 110 a at block 616 may determine whether all the write requests 204 ₁, 204 ₂. . . 204 _nin the chain 200 have completed at both the primary 102 a and secondary 102 b storage servers before returning complete. Further, in mirror/synchronization operations, the I/O manager 110 a may determine an error at block 620 if there is an error in processing the write requests at either the primary 102 a or secondary 102 b storage servers.

The described embodiments provide techniques to process a chain of write requests, such as write request groups each having multiple write transactions, to different storage locations by including a commit wait flag indicating whether the write chain is to be processed as a single logical write, such that a next write request may be processed before the previous one is completed. This allows the command to indicate whether processing should be optimized to increase the speed at which writes are processed by not requiring a commit of a write request before the next write request is processed.

The reference characters used herein, such as i, k, m, and n, are used herein to denote a variable number of instances of an element, which may represent the same or different values, and may represent the same or different value when used with different or the same elements in different described instances.

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

The computational components of FIG. 1, including the host 100 and

storage servers

102 a, 102 b may be implemented in one or more computer systems, such as the computer system 702 shown in FIG. 7. Computer system/server 702 may be described in the general context of computer system executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 702 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 7, the computer system/server 702 is shown in the form of a general-purpose computing device. The components of computer system/server 702 may include, but are not limited to, one or more processors or processing units 704, a system memory 706, and a bus 708 that couples various system components including system memory 706 to processor 704. Bus 708 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 702 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 702, and it includes both volatile and non-volatile media, removable and non-removable media.

System memory

706 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 710 and/or cache memory 712. Computer system/server 702 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 713 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 708 by one or more data media interfaces. As will be further depicted and described below, memory 706 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

Program/utility 714, having a set (at least one) of program modules 716, may be stored in memory 706 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. The components of the computer 702 may be implemented as program modules 716 which generally carry out the functions and/or methodologies of embodiments of the invention as described herein. The systems of FIG. 1 may be implemented in one or more computer systems 702, where if they are implemented in multiple computer systems 702, then the computer systems may communicate over a network.

Computer system/server 702 may also communicate with one or more external devices 718 such as a keyboard, a pointing device, a display 720, etc.; one or more devices that enable a user to interact with computer system/server 702; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 702 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 722. Still yet, computer system/server 702 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 724. As depicted, network adapter 724 communicates with the other components of computer system/server 702 via bus 708. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 702. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

The terms “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the present invention(s)” unless expressly specified otherwise.

The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.

The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.

Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.

A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the present invention.

When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the present invention need not include the device itself.

The foregoing description of various embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims herein after appended.

Claims

What is claimed is:

1. A computer program product for processing a write request chain of write requests to a storage, wherein the computer program product comprises a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause operations, the operations comprising

receiving a write request chain including a commit wait flag and plurality of write requests directed to the storage;

processing the write requests in the write request chain by complete writing for one write request in the write request chain before processing a next write request in the write request chain in response to the commit wait flag indicating to wait; and

processing the write requests by processing the next write request in the write request chain in response to initiating a transfer of data for a write request and before completing the write request in response to the commit wait flag indicating to not wait.

2. The computer program product of claim 1, wherein each write request comprises a write request group having a plurality of write transactions to the storage,

wherein when the commit wait flag indicates to wait, a next write request group in the write request chain is processed after completing all the write transactions in a write request group being processed, and

wherein when the commit wait flag indicates to not wait, a next write request group is processed after initiating processing of the write transactions in a write request group being processed before completing the write transactions in the write request group.

3. The computer program product of claim 2, wherein each write request group includes a locate record domain defining a range of tracks in the storage to which the write transactions in the locate record domain are written.

4. The computer program product of claim 2, wherein processing the write request chain when the commit wait flag indicates to not wait comprises:

for each write request group of write request groups in the write request chain, performing:

processing the write transactions in a write request group;

transferring data for the processed write transactions; and

processing a next write request group in response to initiating the transfer of the data for the write transactions in the write request group being processed when the write request group being processed is not a last write request group in the write request chain.

5. The computer program product of claim 1, wherein the operations further comprise:

returning a final complete status for the write request chain in response to completing all the write requests in the write request chain when the commit wait flag indicates to not wait.

6. The computer program product of claim 1, wherein the computer program product is deployed in a primary storage server and the storage comprises a primary storage coupled to the primary storage server, wherein the primary storage server is in communication with a secondary storage server coupled to a secondary storage, wherein the operations further comprise:

sending a write request being processed at the primary storage server to the secondary storage server to store data from the write request in the secondary storage.

7. The computer program product of claim 6,

wherein when the commit wait flag indicates to commit, the next write request is processed at the primary storage server after completing processing a write request in the write request chain at both the primary and the secondary storage servers, and

wherein when the commit wait flag indicates to not commit, the next write request is processed at the primary storage server and sent to the secondary storage server after initiating the processing of a write request and before completing the processing the write request at the primary and the secondary storage servers.

8. A system in communication with a storage, comprising:

a processor; and

a computer readable storage medium having program instructions embodied therewith, the program instructions executable by the processor to cause operations, the operations comprising:

9. The system of claim 8, wherein each write request comprises a write request group having a plurality of write transactions to the storage,

10. The system of claim 9, wherein each write request group includes a locate record domain defining a range of tracks in the storage to which the write transactions in the locate record domain are written.

11. The system of claim 9, wherein processing the write request chain when the commit wait flag indicates to not wait comprises:

processing the write transactions in a write request group;

transferring data for the processed write transactions; and

12. The system of claim 8, wherein the operations further comprise:

13. The system of claim 8, wherein the program instructions are executed in a primary storage server and the storage comprises a primary storage coupled to the primary storage server, wherein the primary storage server is in communication with a secondary storage server coupled to a secondary storage, wherein the operations further comprise:

14. The system of claim 13,

15. A method for processing a write request chain of write requests to a storage, comprising:

16. The method of claim 15, wherein each write request comprises a write request group having a plurality of write transactions to the storage,

17. The method of claim 16, wherein each write request group includes a locate record domain defining a range of tracks in the storage to which the write transactions in the locate record domain are written.

18. The method of claim 16, wherein processing the write request chain when the commit wait flag indicates to not wait comprises:

processing the write transactions in a write request group;

transferring data for the processed write transactions; and

19. The method of claim 15, further comprising:

20. The method of claim 15, wherein the method is implemented in a computer program product deployed in a primary storage server and the storage comprises a primary storage coupled to the primary storage server, wherein the primary storage server is in communication with a secondary storage server coupled to a secondary storage, further comprising:

21. The method of claim 20,