# Patent

## Title
Contention detection

## Abstract

A multiple computer system is disclosed in which n computers (M1, M2 . . . Mn) each run a different portion of a single application program written to execute only on a single computer. The local memory of each computer is maintained substantially the same by updating all computers with every change made to addressed memory locations. Contention can arise when the same memory location is substantially simultaneously updated by two or more machines because of transmission delays and latency of the communications network interconnecting all the computers. In particular a method of detecting contention is disclosed which utilizes a count value indicative of the number of the sequence of occasions on which each memory location has been updated. Contention is indicated if the currently stored count value and the incoming updating count value are the same.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
The present application claims the benefit under 35 USC 119(e) to U.S. Provisional Application Nos. 60/850,541 and 60/850,711, both filed 9 Oct. 2006. This application claims priority under 35 USC 119(a)-(d) to Australian Provisional Application Nos. 2006905514 and 2006905527, both filed on 5 Oct. 2006, each of which are hereby incorporated herein by reference.
This application is related to concurrently filed U.S. application Ser. No. 11/973,388 filed on 5 Oct. 2007 entitled “Contention Detection,” and to concurrently filed U.S. application Ser. No. 11/973,386 filed on 5 Oct. 2007 entitled “Contention Detection,” issued on 7 Dec. 2010 as U.S. Pat. No. 7,849,151, each of which are hereby incorporated herein by reference.


FIELD OF THE INVENTION
The present invention relates to computing and, in particular, to the detection of contention in computing activities relating to address memory but is not restricted to such activities. The present invention finds particular application to the simultaneous operation of a plurality of computers interconnected via a communications network, and preferably operating in a replicated shared memory arrangement, but is not limited thereto.
BACKGROUND
International Patent Application No. PCT/AU2005/000580 published under WO 2005/103926 (to which U.S. patent application Ser. No. 11/111,946 and published under No. 2005-0262313 corresponds) in the name of the present applicant, discloses how different portions of an application program written to execute on only a single computer can be operated substantially simultaneously on a corresponding different one of a plurality of computers. That simultaneous operation has not been commercially used as of the priority date of the present application. International Patent Applications Nos. PCT/AU2005/001641 (WO2006/110,937) and PCT/AU2006/000532 (WO2006/110,957) both in the name of the present applicant and both unpublished as at the priority date of the present application, also disclose further details. The contents of the specification of each of the abovementioned prior application(s) are hereby incorporated into the present specification by cross reference for all purposes.
Briefly stated, the abovementioned patent specification discloses that at least one application program written to be operated on only a single computer can be simultaneously operated on a number of computers each with independent local memory. The memory locations required for the operation of that program are replicated in the independent local memory of each computer. On each occasion on which the application program writes new data to any replicated memory location, that new data is transmitted and stored at each corresponding memory location of each computer. Thus apart from the possibility of transmission delays, each computer has a local memory the contents of which are substantially identical to the local memory of each other computer and are updated to remain so. Since all application programs, in general, read data much more frequently than they cause new data to be written, the abovementioned arrangement enables very substantial advantages in computing speed to be achieved. In particular, the stratagem enables two or more commodity computers interconnected by a commodity communications network to be operated simultaneously running under the application program written to be executed on only a single computer.
In many situations, the above-mentioned arrangements work satisfactorily. This applies particularly where the programmer is aware that there may be updating delays and so can adjust the flow of the program to account for this. However, the need to update each local memory when any change is made to any memory location, can create contention where corresponding memory locations are being updated in simultaneous or near simultaneous fashion from different sources. This can establish a race condition or similar anomalous conditions. Such conditions can also arise in other computing, information processing, electronics, and electrical engineering situations. It is towards the detection and resolution of contention or a race condition that the present invention is directed.
GENESIS OF THE INVENTION
It is towards the detection of contention or a race condition that the present invention is directed.
SUMMARY OF THE INVENTION
In accordance with a first aspect of the present invention there is disclosed a multiple computer system comprising a multiplicity of computers, each interconnected via at least one communications network, and each executing a different portion of an applications program written to execute on a single computer, each having an independent local memory with at least one memory location being replicated in each said local memory, and a method of detecting contention in replica memory updating in which a memory location having a specific location identifier and replicated on at least two computers, can be updated substantially simultaneously from a plurality of sources, said method comprising the steps of:

    (i) utilizing an updating format for the signal or packet carrying out the updating, said format comprising the specific identifier of the memory location to be updated, the content with which said memory location is to be updated, and a resident updating count of the updating source, said count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating,
    (ii) storing for each replicated memory location the updating count of the previously sent or received updating,
    (iii) comparing the resident updating count associated with the replicated memory location to be updated with the updating count of the currently received updating signal or packet, and
    (iv) indicating a contention situation if the compared updating counts are the same.


In accordance with a second aspect of the present invention there is disclosed a multiple computer system comprising a multiplicity of computers, each interconnected via at least one communications network, and each executing a different portion of an applications program written to execute on a single computer, each having an independent local memory with at least one memory location being replicated in each said local memory, and a system for detecting contention in replica memory updating, said system comprising at least one memory location having a specific location identifier and replicated on at least two machines, and updated to remain substantially similar upon occasion of a machine modifying its replica value; a plurality of sources each of which can update said memory location(s) and each of which utilizes an updating format for the signal or packet carrying out the updating, said format comprising the specific identifier of the memory location to be updated, the content with which said memory location is to be updated, and a resident updating count of the updating source, said count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating; a storage means associated with each said memory location and in which the updating count of the previously received updating is stored; comparison means to compare the previously stored updating count with the updating count of the currently received updating signal or packet; and contention indicating means connected with said comparison means and operable to indicate a contention situation if the compared updating counts are the same.
In accordance with a third aspect of the present invention there is disclosed a multiple computer system comprising a multiplicity of computers, each interconnected via at least one communications network, and each executing a different portion of an applications program written to execute on a single computer, each having an independent local memory with at least one memory location being replicated in each said local memory, and a method of replica memory updating in which a memory location having a specific location identifier and replicated on at least two computers, can be updated substantially simultaneously from a plurality of sources, said method comprising the steps of:

    (i) utilizing an updating format for the signal or packet carrying out the updating, said format comprising the specific identifier of the memory location to be updated, the content with which said memory location is to be updated, and a resident updating count of the updating source, said count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating,
    (ii) storing for each replicated memory location the updating count of the previously sent or received updating,
    (iii) comparing the presently resident updating count associated with the replicated memory location to be updated with the updating count of the currently received updating signal or packet, and
    (iv) if the currently received updating count is greater than the presently resident updating count, overwriting the associated replicated memory location with the currently received data content, and overwriting the presently resident updating count with the currently received updating count, or
    (v) if the currently received updating count is less than the presently resident updating count, not overwriting the associated replicated memory location with the currently received data content, and not overwriting the presently resident updating count with the currently received updating count, or
    (vi) if the currently received updating count is equal to the presently resident updating count, indicating a contention situation.


In accordance with a fourth aspect of the present invention there is disclosed a multiple computer system comprising a multiplicity of computers, each interconnected via at least one communications network, and each executing a different portion of an applications program written to execute on a single computer, each having an independent local memory with at least one memory location being replicated in each said local memory, and a system for replica memory updating, said system comprising at least one memory location having a specific location identifier and replicated on at least two machines, and updated to remain substantially similar upon occasion of a machine modifying its replica value; a plurality of sources each of which can update said memory location(s) and each of which utilizes an updating format for the signal or packet carrying out the updating, said format comprising the specific identifier of the memory location to be updated, the content with which said memory location is to be updated, and a resident updating count of the updating source, said count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating; a storage means associated with each said memory location and in which the updating count of the previously received updating is stored; comparison means to compare the currently received updating count value with the presently resident updating count value and overwriting the associated replicated memory location with the currently received data content and overwriting the presently resident updating count with the currently received updating count, if the currently received updating count exceeds the presently resident updating count, or not overwriting the associated replicated memory location with the currently received data content and not overwriting the presently resident updating count with the currently received updating count, if the currently received updating count is less than the presently resident updating count; and contention indicating means connected with said comparison means and operable to indicate a contention situation if the compared updating counts are the same. Preferably the count comparison means is a comparator.
In accordance with a fifth aspect of the present invention there is disclosed a single computer for use in cooperation with at least one other computer in a multiple computer system, wherein said multiple computer system comprising a multiplicity of computers, each interconnected via at least one communications network, and each executing a different portion of an applications program written to execute on a single computer, each having an independent local memory with at least one memory location being replicated in each said local memory, and a method of replica memory updating in which a memory location having a specific location identifier and replicated on at least two computers, can be updated substantially simultaneously from a plurality of sources, said method comprising the steps of:

    (i) utilizing an updating format for the signal or packet carrying out the updating, said format comprising the specific identifier of the memory location to be updated, the content with which said memory location is to be updated, and a resident updating count of the updating source, said count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating,
    (ii) storing for each replicated memory location the updating count of the previously sent or received updating,
    (iii) comparing the presently resident updating count associated with the replicated memory location to be updated with the updating count of the currently received updating signal or packet, and
    (iv) if the currently received updating count is greater than the presently resident updating count, overwriting the associated replicated memory location with the currently received data content, and overwriting the presently resident updating count with the currently received updating count, or
    (v) if the currently received updating count is less than the presently resident updating count, not overwriting the associated replicated memory location with the currently received data content, and not overwriting the presently resident updating count with the currently received updating count, or
    (vi) if the currently received updating count is equal to the presently resident updating count, indicating a contention situation.





BRIEF DESCRIPTION OF THE DRAWINGS
A preferred embodiment of the present invention will now be described with reference to the drawings in which:
FIG. 1A is a schematic illustration of a prior art computer arranged to operate JAVA code and thereby constitute a single JAVA virtual machine,
FIG. 1B is a drawing similar to FIG. 1A but illustrating the initial loading of code,
FIG. 1C illustrates the interconnection of a multiplicity of computers each being a JAVA virtual machine to form a multiple computer system,
FIG. 2 schematically illustrates “n” application running computers to which at least one additional server machine X is connected as a server,
FIGS. 3-5 illustrate the steps of in due course updating memory locations,
FIGS. 6 and 7 illustrate the stages by which contention can occur,
FIGS. 8-12 illustrate the stages of an embodiment whereby contention can be detected,
FIGS. 13, 14, 15, 16, 17 and 18 illustrate various time graphs of replica update transmissions,
FIG. 19 illustrates a preferred arrangement of storing “count values”,
FIGS. 20, 21 and 22 illustrate two arrangements of replicated shared memory multiple computer systems, and
FIG. 23 illustrates an alternative arrangement of replicated memory instances.



DETAILED DESCRIPTION
The embodiments will be described with reference to the JAVA language, however, it will be apparent to those skilled in the art that the invention is not limited to this language and, in particular can be used with other languages (including procedural, declarative and object oriented languages) including the MICROSOFT.NET platform and architecture (Visual Basic, Visual C, and Visual C++, and Visual C#), FORTRAN, C, C++, COBOL, BASIC and the like.
It is known in the prior art to provide a single computer or machine (produced by any one of various manufacturers and having an operating system operating in any one of various different languages) utilizing the particular language of the application by creating a virtual machine as illustrated in FIG. 1A.
The code and data and virtual machine configuration or arrangement of FIG. 1A takes the form of the application code 50 written in the JAVA language and executing within the JAVA virtual machine 61. Thus where the intended language of the application is the language JAVA, a JAVA virtual machine is used which is able to operate code in JAVA irrespective of the machine manufacturer and internal details of the computer or machine.
For further details, see “The JAVA Virtual Machine Specification” 2nd Edition by T. Lindholm and F. Yellin of Sun Microsystems Inc of the USA which is incorporated herein by reference.
This conventional art arrangement of FIG. 1A is modified by the present applicant by the provision of an additional facility which is conveniently termed a “distributed run time” or a “distributed run time system” DRT 71 and as seen in FIG. 1B.
In FIGS. 1B and 1C, the application code 50 is loaded onto the Java Virtual Machine(s) M1, M2, . . . Mn in cooperation with the distributed runtime system 71, through the loading procedure indicated by arrow 75 or 75A or 75B. As used herein the terms “distributed runtime” and the “distributed run time system” are essentially synonymous, and by means of illustration but not limitation are generally understood to include library code and processes which support software written in a particular language running on a particular platform. Additionally, a distributed runtime system may also include library code and processes which support software written in a particular language running within a particular distributed computing environment. The runtime system typically deals with the details of the interface between the program and the operating system such as system calls, program start-up and termination, and memory management. For purposes of background, a conventional Distributed Computing Environment (DCE) (that does not provide the capabilities of the inventive distributed run time or distributed run time system 71 used in the preferred embodiments of the present invention) is available from the Open Software Foundation. This Distributed Computing Environment (DCE) performs a form of computer-to-computer communication for software running on the machines, but among its many limitations, it is not able to implement the desired modification or communication operations. Among its functions and operations the preferred DRT 71 coordinates the particular communications between the plurality of machines M1, M2, . . . Mn. Moreover, the preferred distributed runtime 71 comes into operation during the loading procedure indicated by arrow 75A or 75B of the JAVA application 50 on each JAVA virtual machine 72 or machines JVM#1, JVM#2, . . . JVM#n of FIG. 1C. It will be appreciated in light of the description provided herein that although many examples and descriptions are provided relative to the JAVA language and JAVA virtual machines so that the reader may get the benefit of specific examples, there is no restriction to either the JAVA language or JAVA virtual machines, or to any other language, virtual machine, machine or operating environment.
FIG. 1C shows in modified form the arrangement of the JAVA virtual machines, each as illustrated in FIG. 1B. It will be apparent that again the same application code 50 is loaded onto each machine M1, M2 . . . Mn. However, the communications between each machine M1, M2 . . . Mn are as indicated by arrows 83, and although physically routed through the machine hardware, are advantageously controlled by the individual DRT's 71/1 . . . 71/n within each machine. Thus, in practice this may be conceptionalised as the DRT's 71/1, . . . 71/n communicating with each other via the network or other communications link 53 rather than the machines M1, M2 . . . Mn communicating directly themselves or with each other. Contemplated and included are either this direct communication between machines M1, M2 . . . Mn or DRT's 71/1, 71/2 . . . 71/n or a combination of such communications. The preferred DRT 71 provides communication that is transport, protocol, and link independent.
The one common application program or application code 50 and its executable version (with likely modification) is simultaneously or concurrently executing across the plurality of computers or machines M1, M2 . . . Mn. The application program 50 is written with the intention that it only operate on a single machine or computer. Essentially the modified structure is to replicate an identical memory structure and contents on each of the individual machines.
The term common application program is to be understood to mean an application program or application program code written to operate on a single machine, and loaded and/or executed in whole or in part on each one of the plurality of computers or machines M1, M2 . . . Mn, or optionally on each one of some subset of the plurality of computers or machines M1, M2 . . . Mn. Put somewhat differently, there is a common application program represented in application code 50. This is either a single copy or a plurality of identical copies each individually modified to generate a modified copy or version of the application program or program code. Each copy or instance is then prepared for execution on the corresponding machine. At the point after they are modified they are common in the sense that they perform similar operations and operate consistently and coherently with each other. It will be appreciated that a plurality of computers, machines, information appliances, or the like implementing the above described arrangements may optionally be connected to or coupled with other computers, machines, information appliances, or the like that do not implement the above described arrangements.
The same application program 50 (such as for example a parallel merge sort, or a computational fluid dynamics application or a data mining application) is run on each machine, but the executable code of that application program is modified on each machine as necessary such that each executing instance (copy or replica) on each machine coordinates its local operations on that particular machine with the operations of the respective instances (or copies or replicas) on the other machines such that they function together in a consistent, coherent and coordinated manner and give the appearance of being one global instance of the application (i.e. a “meta-application”).
The copies or replicas of the same or substantially the same application codes, are each loaded onto a corresponding one of the interoperating and connected machines or computers. As the characteristics of each machine or computer may differ, the application code 50 may be modified before loading, or during the loading process, or with some disadvantages after the loading process, to provide a customization or modification of the code on each machine. Some dissimilarity between the programs may be permitted so long as the other requirements for interoperability, consistency, and coherency as described herein can be maintained. As it will become apparent hereafter, each of the machines M1, M2 . . . Mn and thus all of the machines M1, M2 . . . Mn have the same or substantially the same application code 50, usually with a modification that may be machine specific.
Before the loading of, or during the loading of, or at any time preceding the execution of, the application code 50 (or the relevant portion thereof) on each machine M1, M2 . . . Mn, each application code 50 is modified by a corresponding modifier 51 according to the same rules (or substantially the same rules since minor optimizing changes are permitted within each modifier 51/1, 51/2 . . . 51/n).
Each of the machines M1, M2 . . . Mn operates with the same (or substantially the same or similar) modifier 51 (in some embodiments implemented as a distributed run time or DRT71 and in other embodiments implemented as an adjunct to the code and data 50, and also able to be implemented within the JAVA virtual machine itself). Thus all of the machines M1, M2 . . . Mn have the same (or substantially the same or similar) modifier 51 for each modification required. A different modification, for example, may be required for memory management and replication, for initialization, for finalization, and/or for synchronization (though not all of these modification types may be required for all embodiments).
There are alternative implementations of the modifier 51 and the distributed run time 71. For example as indicated by broken lines in FIG. 1C, the modifier 51 may be implemented as a component of or within the distributed run time 71, and therefore the DRT 71 may implement the functions and operations of the modifier 51. Alternatively, the function and operation of the modifier 51 may be implemented outside of the structure, software, firmware, or other means used to implement the DRT 71 such as within the code and data 50, or within the JAVA virtual machine itself. In one embodiment, both the modifier 51 and DRT 71 are implemented or written in a single piece of computer program code that provides the functions of the DRT and modifier. In this case the modifier function and structure is, in practice, subsumed into the DRT. Independent of how it is implemented, the modifier function and structure is responsible for modifying the executable code of the application code program, and the distributed run time function and structure is responsible for implementing communications between and among the computers or machines. The communications functionality in one embodiment is implemented via an intermediary protocol layer within the computer program code of the DRT on each machine. The DRT can, for example, implement a communications stack in the JAVA language and use the Transmission Control Protocol/Internet Protocol (TCP/IP) to provide for communications or talking between the machines. Exactly how these functions or operations are implemented or divided between structural and/or procedural elements, or between computer program code or data structures, is not crucial.
However, in the arrangement illustrated in FIG. 1C, a plurality of individual computers or machines M1, M2 . . . Mn are provided, each of which are interconnected via a communications network 53 or other communications link. Each individual computer or machine is provided with a corresponding modifier 51. Each individual computer is also provided with a communications port which connects to the communications network. The communications network 53 or path can be any electronic signalling, data, or digital communications network or path and is preferably a slow speed, and thus low cost, communications path, such as a network connection over the Internet or any common networking configurations including communications ports known or available as of the date of this application such as ETHERNET or INFINIBAND and extensions and improvements, thereto. Preferably the computers are provided with known communication ports (such as CISCO Power Connect 5224 Switches) which connect with the communications network 53.
As a consequence of the above described arrangement, if each of the machines M1, M2, . . . , Mn has, say, an internal or local memory capability of 10 MB, then the total memory available to the application code 50 in its entirety is not, as one might expect, the number of machines (n) times 10 MB. Nor is it the additive combination of the internal memory capability of all n machines. Instead it is either 10 MB, or some number greater than 10 MB but less than n×10 MB. In the situation where the internal memory capacities of the machines are different, which is permissible, then in the case where the internal memory in one machine is smaller than the internal memory capability of at least one other of the machines, then the size of the smallest memory of any of the machines may be used as the maximum memory capacity of the machines when such memory (or a portion thereof) is to be treated as ‘common’ memory (i.e. similar equivalent memory on each of the machines M1 . . . Mn) or otherwise used to execute the common application code.
However, even though the manner that the internal memory of each machine is treated may initially appear to be a possible constraint on performance, how this results in improved operation and performance will become apparent hereafter. Naturally, each machine M1, M2 . . . Mn has a private (i.e. ‘non-common’) internal memory capability. The private internal memory capability of the machines M1, M2, . . . , Mn are normally approximately equal but need not be.
Non-commercial operation of a prototype multiple computer system indicates that not every machine or computer in the system utilises or needs to refer to (e.g. have a local replica of) every possible memory location. As a consequence, it is possible to operate a multiple computer system without the local memory of each machine being identical to every other machine, so long as the local memory of each machine is sufficient for the operation of that machine. That is to say, provided a particular machine does not need to refer to (for example have a local replica of) some specific memory locations, then it does not matter that those specific memory locations are not replicated in that particular machine.
It may also be advantageous to select the amounts of internal memory in each machine to achieve a desired performance level in each machine and across a constellation or network of connected or coupled plurality of machines, computers, or information appliances M1, M2, . . . , Mn. Having described these internal and common memory considerations, it will be apparent in light of the description provided herein that the amount of memory that can be common between machines is not a limitation.
In some embodiments, some or all of the plurality of individual computers or machines can be contained within a single housing or chassis (such as so-called “blade servers” manufactured by Hewlett-Packard Development Company, Intel Corporation, IBM Corporation and others) or the multiple or dual core processor or machines manufactured by Intel, AMD, or others, or implemented on a single printed circuit board or even within a single chip or chip set.
When implemented in a non-JAVA language or application code environment, the generalized platform, and/or virtual machine and/or machine and/or runtime system is able to operate application code 50 in the language(s) (possibly including for example, but not limited to any one or more of source-code languages, intermediate-code languages, object-code languages, machine-code languages, and any other code languages) of that platform and/or virtual machine and/or machine and/or runtime system environment, and utilize the platform, and/or virtual machine and/or machine and/or runtime system and/or language architecture irrespective of the machine manufacturer and the internal details of the machine. It will also be appreciated that the platform and/or runtime system can include virtual machine and non-virtual machine software and/or firmware architectures, as well as hardware and direct hardware coded applications and implementations.
For a more general set of virtual machine or abstract machine environments, and for current and future computers and/or computing machines and/or information appliances or processing systems, and that may not utilize or require utilization of either classes and/or objects, the structure, method and computer program and computer program product are still applicable. Examples of computers and/or computing machines that do not utilize either classes and/or objects include for example, the x86 computer architecture manufactured by Intel Corporation and others, the SPARC computer architecture manufactured by Sun Microsystems, Inc and others, the Power PC computer architecture manufactured by International Business Machines Corporation and others, and the personal computer products made by Apple Computer, Inc., and others.
For these types of computers, computing machines, information appliances, and the virtual machine or virtual computing environments implemented thereon that do not utilize the idea of classes or objects, may be generalized for example to include primitive data types (such as integer data types, floating point data types, long data types, double data types, string data types, character data types and Boolean data types), structured data types (such as arrays and records), derived types, or other code or data structures of procedural languages or other languages and environments such as functions, pointers, components, modules, structures, reference and unions. These structures and procedures when applied in combination when required, maintain a computing environment where memory locations, address ranges, objects, classes, assets, resources, or any other procedural or structural aspect of a computer or computing environment are where required created, maintained, operated, and deactivated or deleted in a coordinated, coherent, and consistent manner across the plurality of individual machines M1, M2 . . . Mn.
This analysis or scrutiny of the application code 50 can take place either prior to loading the application program code 50, or during the application program code 50 loading procedure, or even after the application program code 50 loading procedure. It may be likened to an instrumentation, program transformation, translation, or compilation procedure in that the application code can be instrumented with additional instructions, and/or otherwise modified by meaning-preserving program manipulations, and/or optionally translated from an input code language to a different code language (such as for example from source-code language or intermediate-code language to object-code language or machine-code language). In this connection it is understood that the term “compilation” normally or conventionally involves a change in code or language, for example, from source code to object code or from one language to another language. However, in the present instance the term “compilation” (and its grammatical equivalents) is not so restricted and can also include or embrace modifications within the same code or language. For example, the compilation and its equivalents are understood to encompass both ordinary compilation (such as for example by way of illustration but not limitation, from source-code to object code), and compilation from source-code to source-code, as well as compilation from object-code to object code, and any altered combinations therein. It is also inclusive of so-called “intermediary-code languages” which are a form of “pseudo object-code”.
By way of illustration and not limitation, in one arrangement, the analysis or scrutiny of the application code 50 takes place during the loading of the application program code such as by the operating system reading the application code 50 from the hard disk or other storage device or source and copying it into memory and preparing to begin execution of the application program code. In another embodiment, in a JAVA virtual machine, the analysis or scrutiny may take place during the class loading procedure of the java.lang.ClassLoader.loadClass method (e.g. “java.lang.ClassLoader.loadClass( )”).
Alternatively, the analysis or scrutiny of the application code 50 may take place even after the application program code loading procedure, such as after the operating system has loaded the application code into memory, or optionally even after execution of the relevant corresponding portion of the application program code has started, such as for example after the JAVA virtual machine has loaded the application code into the virtual machine via the “java.lang.ClassLoader.loadClass( )” method and optionally commenced execution.
Persons skilled in the computing arts will be aware of various possible techniques that may be used in the modification of computer code, including but not limited to instrumentation, program transformation, translation, or compilation means.
One such technique is to make the modification(s) to the application code, without a preceding or consequential change of the language of the application code. Another such technique is to convert the original code (for example, JAVA language source-code) into an intermediate representation (or intermediate-code language, or pseudo code), such as JAVA byte code. Once this conversion takes place the modification is made to the byte code and then the conversion may be reversed. This gives the desired result of modified JAVA code.
A further possible technique is to convert the application program to machine code, either directly from source-code or via the abovementioned intermediate language or through some other intermediate means. Then the machine code is modified before being loaded and executed. A still further such technique is to convert the original code to an intermediate representation, which is thus modified and subsequently converted into machine code. All such modification routes are envisaged and also a combination of two, three or even more, of such routes.
The DRT or other code modifying means is responsible for creating or replication a memory structure and contents on each of the individual machines M1, M2 . . . Mn that permits the plurality of machines to interoperate. In some arrangements this replicated memory structure will be identical. Whilst in other arrangements this memory structure will have portions that are identical and other portions that are not. In still other arrangements the memory structures are different only in format or storage conventions such as Big Endian or Little Endian formats or conventions.
These structures and procedures when applied in combination when required, maintain a computing environment where the memory locations, address ranges, objects, classes, assets, resources, or any other procedural or structural aspect of a computer or computing environment are where required created, maintained, operated, and deactivated or deleted in a coordinated, coherent, and consistent manner across the plurality of individual machines M1, M2 . . . Mn.
Therefore the terminology “one”, “single”, and “common” application code or program includes the situation where all machines M1, M2 . . . Mn are operating or executing the same program or code and not different (and unrelated) programs, in other words copies or replicas of same or substantially the same application code are loaded onto each of the interoperating and connected machines or computers.
In conventional arrangements utilising distributed software, memory access from one machine's software to memory physically located on another machine takes place via the network interconnecting the machines. However, because the read and/or write memory access to memory physically located on another computer require the use of the slow network interconnecting the computers, in these configurations such memory accesses can result in substantial delays in memory read/write processing operations, potentially of the order of 106-107 cycles of the central processing unit of the machine. Ultimately this delay is dependent upon numerous factors, such as for example, the speed, bandwidth, and/or latency of the communication network. This in large part accounts for the diminished performance of the multiple interconnected machines in the prior art arrangement.
However, in the present arrangement all reading of memory locations or data is satisfied locally because a current value of all (or some subset of all) memory locations is stored on the machine carrying out the processing which generates the demand to read memory.
Similarly, all writing of memory locations or data is satisfied locally because a current value of all (or some subset of all) memory locations is stored on the machine carrying out the processing which generates the demand to write to memory.
Such local memory read and write processing operation can typically be satisfied within 102-103 cycles of the central processing unit. Thus, in practice there is substantially less waiting for memory accesses which involves and/or writes.
The arrangement is transport, network, and communications path independent, and does not depend on how the communication between machines or DRTs takes place. Even electronic mail (email) exchanges between machines or DRTs may suffice for the communications.
Non-commercial operation of a prototype multiple computer system indicates that not every machine or computer in the system utilises or needs to refer to (eg have a local replica of) every possible memory location. As a consequence, it is possible to operate a multiple computer system without the local memory of each machine being identical to every other machine, so long as the local memory of each machine is sufficient for the operation of that machine. That is to say, provided a particular machine does not need to refer to (for example have a local replica of) some specific memory locations, then it does not matter that those specific memory locations are not replicated in that particular machine.
In connection with the above, it will be seen from FIG. 2 that there are a number of machines M1, M2, . . . Mn, n being an integer greater than or equal to two, on which the application program 50 of FIG. 1 is being run substantially simultaneously, and there is preferably a further machine X which is provided to enable various housekeeping functions to be carried out, such as acting as a lock server. In particular, the further machine X can be a low value machine, and much less expensive than the other machines which can have desirable attributes such as processor speed. Furthermore, an additional low value machine (X+1) is preferably available to provide redundancy in case machine X should fail. Where two such server machines X and X+1 are provided, they are preferably, for reasons of simplicity, operated as dual machines in a cluster configuration. Machines X and X+1 could be operated as a multiple computer system in accordance with the abovedescribed arrangements, if desired. However this would result in generally undesirable complexity. If the machine X is not provided then its functions, such as housekeeping functions, are provided by one, or some, or all of the other machines.
FIG. 20 is a schematic diagram of a replicated shared memory system. In FIG. 20 three machines are shown, of a total of “n” machines (n being an integer greater than one) that is machines M1, M2, . . . Mn. Additionally, a communications network 53 is shown interconnecting the three machines and a preferable (but optional) server machine X which can also be provided and which is indicated by broken lines. In each of the individual machines, there exists a memory N8102 and a CPU N8103. In each memory N8102 there exists three memory locations, a memory location A, a memory location B, and a memory location C. Each of these three memory locations is replicated in a memory N8102 of each machine.
This arrangement of the replicated shared memory system allows a single application program written for, and intended to be run on, a single machine, to be substantially simultaneously executed on a plurality of machines, each with independent local memories, accessible only by the corresponding portion of the application program executing on that machine, and interconnected via the network 53. In International Patent Application No. PCT/AU2005/001641 (WO 2006/110,937) to which U.S. patent application Ser. No. 11/259,885 entitled: “Computer Architecture Method of Operation for Multi-Computer Distributed Processing and Co-ordinated Memory and Asset Handling” corresponds and PCT/AU2006/000532 (WO 2006/110,957) in the name of the present applicant, a technique is disclosed to detect modifications or manipulations made to a replicated memory location, such as a write to a replicated memory location A by machine M1 and correspondingly propagate this changed value written by machine M1 to the other machines M2. Mn which each have a local replica of memory location A. This result is achieved by the preferred embodiment of detecting write instructions in the executable object code of the application to be run that write to a replicated memory location, such as memory location A, and modifying the executable object code of the application program, at the point corresponding to each such detected write operation, such that new instructions are inserted to additionally record, mark, tag, or by some such other recording means indicate that the value of the written memory location has changed.
An alternative arrangement is that illustrated in FIG. 21 and termed partial or hybrid replicated shared memory (RSM). Here memory location A is replicated on computers or machines M1 and M2, memory location B is replicated on machines M1 and Mn, and memory location C is replicated on machines M1, M2 and Mn. However, the memory locations D and E are present only on machine M1, the memory locations F and G are present only on machine M2, and the memory locations Y and Z are present only on machine Mn. Such an arrangement is disclosed in International Patent Application No. PCT/AU2006/001447 published under WO 2007/041762 (and to which U.S. patent application Ser. No. 11/583,958). In such a partial or hybrid RSM systems changes made by one computer to memory locations which are not replicated on any other computer do not need to be updated at all. Furthermore, a change made by any one computer to a memory location which is only replicated on some computers of the multiple computer system need only be propagated or updated to those some computers (and not to all other computers).
Consequently, for both RSM and partial RSM, a background thread task or process is able to, at a later stage, propagate the changed value to the other machines which also replicate the written to memory location, such that subject to an update and propagation delay, the memory contents of the written to memory location on all of the machines on which a replica exists, are substantially identical. Various other alternative embodiments are also disclosed in the abovementioned prior art. Whilst the above prior art methods are adequate for application programs which write infrequently to replicated memory locations, the prior art method is prone to inherent inefficiencies in those application programs which write frequently to replicated memory locations.
All described embodiments and arrangements of the present invention are equally applicable to replicated shared memory systems, whether partially replicated or not. Specifically, partially replicated shared memory arrangements where some plurality of memory locations are replicated on some subset of the total machines operating in the replicated shared memory arrangement, themselves may constitute a replicated shared memory arrangement for the purposes of this invention.
In FIG. 3 a number, “n”, of application running computers or machines M1, M2, M3 . . . Mn are provided and, if desired, a server machine X can also be provided. Since the server machine is not essential it is indicated in phantom in FIG. 3. All the machines M1-Mn, and X if present, are interconnected in some fashion, preferably via a commodity communications network 53. In each of the application running machines, there are replicated memory locations which, for the sake of this discussion, will be restricted to two in number and which have addresses/identifiers of #15 and #16 respectively (but which need not be sequential). Each replicated memory location has a content or value which in some instances can include code but again for the purposes of this discussion will be deemed to constitute merely a number having a numerical value. The content of replica memory location/address #15 is the value (number) 107 and the content of replica memory location/address #16 is the value (number) 192. Each of the n application running machines has the two replicated memory locations and each replica memory location in each machine has substantially the same content or number.
Turning now to FIG. 4, the situation which arises when a change in the content of a specific replicated memory location of one of the machines occurs, is explained. For the purposes of this description, it is assumed that machine M1 in executing its portion of the application program 50, carries out a memory write which results in the content of replica memory location/address #15 of machine M1 being changed from the value (number) 107 to the value (number) 211. This change is then notified (updated) to all other machines M2, M3 . . . Mn via the network 53, such as in accordance with the above mentioned specifications and/or description for updating of replicated memory locations. This is schematically illustrated in FIG. 4 by the sending of an update notification from machine M1 to all the other machines on which a corresponding replica memory location resides, of the identity or address of the modified replica memory location with the changed content, and also the new changed content. This message is schematically illustrated as message 61 in FIG. 4.
In FIG. 5, the message 61 from machine M1 of FIG. 4 has passed through the network 53 and been received by each of the other machines M2, M3 . . . Mn, which on receipt of the message 61 utilize an overwrite means or arrangement to store the changed content 211 in the local replica memory location corresponding to address #15. In this connection it should be understood that the actual address in each of the machines M1-Mn may be different from each other machine but that each of the replica memory locations has a substantially similar global identifier or global address. Preferably, the local memory address and the global memory identifier/address are recorded or tabulated either in tables maintained by each of the machines M1-Mn, or in the server machine X. In FIG. 5, the updating has been successfully carried out and all machines M2, M3 . . . Mn have been consistently updated to take into account the change brought about by (and within) machine M1.
Turning now to FIG. 13, the example of FIGS. 4-5 is collectively illustrated in a time-diagram. Here, machine M1 transmits replica memory update N101 (which corresponds to replica update 61 of FIGS. 4 and 5) at time-unit 1, with the updated value “211” of address #15, to machines M2, M3 . . . Mn on which corresponding replica memory locations reside. However, as is indicated in FIG. 13, transmission N101 does not arrive at the receiving machines M2-Mn immediately (that is, at the same time-unit 1 of transmission). Instead, each receiving machine is indicated to receive replica update transmission N101 at time-unit 5 by the arrows shown for each machine M2-Mn.
Thus, FIG. 13 illustrates a time-delay that typically results between transmission and receipt of a replica memory update, due to latency and delay of the communications network used to interconnect and transmit the replica memory updates between the multiple computers of the multiple computer system. This period of delay, N110, represents the “transmission latency/delay” between the sending of replica update transmission N101 by machine M1, and the receipt of the same replica update transmission N101 by machines M2-Mn.
Following transmission N101 at time-unit 1, at time-unit 5 the receiving machines M2, M3 . . . Mn each independently receive the transmission N101, and update their local corresponding replica memory locations of address #15 with the received updated replica value “211” of transmission N101.
Thus in the circumstances where only a single machine at a time updates a replica memory address(es)/location(s) of other machines with changed value(s) or content, then no conflict or inconsistency arises (or will arise) between the values of the replicated memory locations on all the machines M1, M2, M3 . . . Mn.
For example, consider FIG. 14. FIG. 14 follows on from FIG. 13, where at time-unit 7, and following receipt of transmission N101, machine M3 transmits replica memory update N102, with the updated value “999” of address #15, to machines M1, M2, M4 . . . Mn. As all machines M2-Mn are indicated to have received transmission N101 prior to transmission N102, then no potential inconsistency or conflict will arise between transmissions N101 and N102. Thus, consistent and coherent updating of replicated memory locations is preserved in cases where only a single machine at a time updates a replicated memory location.
However, it is possible for the content of a single replica memory location/address, say address #15, to be modified (written-to) simultaneously, or substantially simultaneously, by two machines, say M1 and M3. The term “substantially simultaneously” as used herein is used to refer to events which happen at the same time, or concurrently, or to events which are nearly simultaneous or nearly concurrent. In the example to be described hereafter the new content of replica memory location/address #15 written by machine M1 is the value/number 404 and the new content of replica memory location/address #15 of machine M3 is the value/number 92. As a consequence of their execution of their different portions of the application program 50, the two machines M1 and M3 modifying the same replica memory location/address #15, substantially simultaneously/concurrently send a update notification 81 and 82 respectively via the network 53 to all the other machines. These update notifications are intended to update the corresponding replica memory locations of all other machines in the manner indicated in FIG. 6.
In FIG. 7, machine M1 which has just changed (written) its content at replica memory location/address #15 to value/number 404, now receives update message 82 from machine M3 and therefore in accordance with the replica updating method of FIG. 5 updates its value/content of replica memory location/address #15 to be the value/number 92. Similarly, machine M3 which has just updated (written) its content at replica memory location/address #15 to the value/number 92, then receives the update message 81 from machine M1 and thus updates its value/content of replica memory location/address #15 to be the value/number 404.
However, each of the other machines M2, M4, M5 . . . Mn receives both messages 81 and 82 (in either order, and potentially dissimilar orders, depending upon the speed and latency of the network 53). Thus the value/content appearing at replica memory location/address #15 for these machines will be either the value/number 404 or 92 depending upon whether message 81 or message 82 was received last.
Clearly, the consequence of the circumstances described above in relation to FIG. 7 is that the memory values/contents for corresponding replica memory locations/addresses of the plural machines M1-Mn are no longer consistent. Machines M1 and M3 will have swapped values caused by the receipt of each other's update notification of each other machine's change, whilst the remaining machines will each independently have either one or the other of the values of the two message originating machines (M1 and M3 in this example). It follows that in circumstances where updating messages are issued simultaneously, or nearly simultaneously, it is not possible to guarantee that the replicated memory locations on all of the machines M1, M2 . . . Mn will be updated in a consistent and coherent manner, and consequently that all machines will have consistent contents or values for the same replicated memory location(s). Therefore the desirable behaviour of consistently updated replicated memory locations of plural machines, and the desirable state of consistent replicated memory locations of plural machines, is not achieved and/or is not guaranteed to be achieved.
It will be apparent that such contention/inconsistency arises because of differences in timing caused by latency/delay and/or ordering of network transmissions. FIG. 15 illustrates how such latency/delay of network transmissions can cause the “contention/inconsistency” case of FIGS. 6-7.
Turning thus to FIG. 15, the example of FIGS. 6-7 is collectively illustrated in a time-diagram. Here, machine M1 transmits replica memory update N301 (which corresponds to replica update 81 of FIGS. 6 and 7), with the updated value “404” of address #15, to machines M2, M3 . . . Mn on which corresponding replica memory locations reside. Also, substantially simultaneously/concurrently machine M3 also transmits a replica memory update N302 (which corresponds to replica update 82 of FIGS. 6 and 7), with the updated value “92” of the same address #15, to machines M1, M2, M4 . . . Mn on which corresponding replica memory locations reside.
However, as is indicated in FIG. 15, transmissions N301 and N302 do not arrive at the receiving machines immediately (that is, at the same time-unit 1 of transmission). Instead, each receiving machine is indicated to receive replica update transmissions N301 and N302 at time-unit 5 by the arrows shown for each machine M1-Mn.
The problem of such contention/conflict between plural replica update transmissions of FIGS. 6-7, arises due to the latency and delay of network communication through the network 53 interconnecting the multiple computers. Specifically, where there is a latency/delay (e.g. N310 of FIG. 15) between transmission and receipt of a replica update transmission, such delay represents a “blind-spot” of a first transmitting machine (e.g. machine M1) attempting a replica update transmission for a specific replicated memory location, as such first machine is not able to know at the time of transmission (e.g. time-unit 1) whether a second (or more) machine (e.g. machine M3) has already transmitted a yet to be received replica update transmission for the same specific replicated memory location (such as transmitted prior to time-unit 1), or is currently transmitting a replica update transmission for the same specific replicated memory location (such for example transmission N302 at time-unit 1), or will transmit prior to receipt of the first machine's transmission a replica update transmission for the same specific replicated memory location (such as for example transmitted at time-units 2-4). Such a “blind spot” (or “contention window”) is indicated as the shaded area N310 of FIG. 15.
Consequently, two or more replica update transmission(s) for a same replicated memory location(s) transmitted during such a “blind spot” (or “contention window”), may be or will be at risk of “conflicting” with one another, thus potentially resulting in inconsistent updating of such replicated memory location(s) of the plural machines if undetected.
Thus, FIG. 15 illustrates the case of the two machines M1 and M3 of FIGS. 6-7 each transmitting a replica memory update for a same replicated memory location (address #15) at a substantially simultaneous time, where each transmitting machine does not know in advance of transmission that another machine is also transmitting a replica memory update for the same replicated memory location.
The time-delay N310 that results between transmission and receipt of each machine's replica memory update, due to latency and delay of the communications network used to interconnect and transmit the replica memory updates between the multiple computers of the multiple computer system, represents a “blind spot” (or “contention window”) where potential transmissions by other machines are not able to be known or detected until some-time later (e.g. upon receipt of such other potential transmissions, such as time-unit 5 when the “blind-spot” N310 is indicated to end). This period of delay, N310, represents the “transmission latency/delay” between the sending of replica update transmissions N301 and N302 by machines M1 and M3, and the receipt of each replica update transmission by the receiving machines.
Therefore, in order to overcome the risk of inconsistent replica updating of FIGS. 6-7, it is necessary to conceive a method to detect multiple transmissions for a same replicated memory location/address #15 which are (or were) transmitted substantially simultaneously/concurrently, such as during the “blind spot” (or “contention window”) N310 of FIG. 15—for example, detecting two or more replica update transmissions (sent by two or more machines) for a same replicated memory location which were each sent prior to the receipt of each other machine's transmission(s) (or prior to receipt of all transmission(s) of one or more of the other machine(s)).
Most solutions of such contention/inconsistency problems rely upon time stamping or a synchronizing clock signal (or other synchronization means) which is common to all machines/computers (entities) involved. However, in the multiple computer environment in which the preferred embodiment of the present invention arises, there is no synchronizing signal common to all the computers (as each computer is independent). Similarly, although each computer has its own internal time keeping mechanism, or clock, these are not synchronized (and even if they could be, would not reliably stay synchronized since each clock may run at a slightly different rate or speed, potentially resulting in undesirable clock-skew and/or clock-drift between the plural machines). Thus solutions based on time or attempted synchronization between plural machines are bound to be complex and/or inefficient and/or are not likely to succeed or will/may result in undesirable/unsatisfactory overhead. Instead, the preferred embodiment utilizes the concept of sequence, rather than time.
In conceiving of a means or method to overcome the abovedescribed undesirable behaviour, it is desirable that such solution not impose significant overhead on the operation of the multiple computer system—either in terms of additional communication overhead (such as additional transmissions in order to detect the potential for conflicting updates, or avoid such conflicting updates from occurring in the first place), or in terms of additional or delayed processing by sending and/or receiving machine(s) (such as additional or delayed processing by receiving machines of one or more received transmissions, or additional or delayed processing by sending machines of one or more to-be-sent transmissions).
For example, it is desirable that receiving machines be permitted to receive and action packets/transmissions in any order (including an order different to the order in which such transmission/packets were sent), and potentially different orders for the same plural transmissions on different receiving machines. This is desirable, because a requirement to process/action received transmissions in specific/fixed orders imposes additional undesirable overhead and delay in processing of received transmissions, such as for example delayed processing/actioning of a later sent but earlier received transmission until receipt and processing/actioning of an earlier sent but later received (or yet-to-be-received) transmission.
Specifically, one example of a prior art method of addressing the above described problem would be to cause each receiving machine to store received replica update transmission in a temporary buffer memory to delay the actioning of such received replica update transmissions. Specifically, such received update transmissions are stored in such a temporary buffer memory for some period of time (for example one second) in which the receiving machine waits for potentially one or more conflicting replica update transmissions to be received. If no such conflicting replica update transmissions are received within such period of time, then the received transmission(s) stored in the temporary buffer memory may be proceeded to be actioned (where such actioning results in the updating of replica memory locations of the receiving machine). Alternatively, if one or more conflicting replica update transmissions are received, then signalling that a conflicting replica update transmission(s) has been received. However, such prior art method is undesirable as additional delay (namely, storing received transmissions in a temporary buffer memory and not processing/actioning them for a period of time) is caused by such prior art method.
In accordance with a first embodiment of the present invention, this problem is addressed (no pun intended) by the introduction of a “count value” (or logical sequencing value) associated with each replicated memory location (or alternatively two or more replicated memory locations of a related set of replicated memory locations). The modified position is schematically illustrated in FIG. 8 where each of the replicated memory locations/addresses #15 and #16 is provided with a “count value”. In the particular instance illustrated in FIG. 8, the content of replicated memory location/address #15 is 107 and its “count value” is 7 whilst the content of replicated memory location/address #16 is 192 and its “count value” is 84.
In FIG. 9, the operation of machine M1 causes the content of address #15 to be changed from 107 to 211. Following such write operation, such as upon transmission of message 73 (or some time prior to transmission of message 73), the count value associated with address #15 is incremented from 7 to 8. This indicates that message 73 is the next logical update message in the sequence of update messages of address #15 known to machine M1 at the time of transmission of message 73. Machine M1 then sends a message 73 via the network 53 to all other application running machines M2, M3 . . . Mn to instruct them to update their content for their corresponding replica memory location/address #15.
This is exactly what happens as illustrated in FIG. 10 in which the single message 73 is received by all of the other machines M2, M3 . . . Mn so that address #15 for all these receiving machines are updated with the new content 211, and the new count value 8. Thus, FIG. 10 indicates the receipt of message 73 by all other machines M2 . . . Mn, and the “actioning” of such received message 73 in accordance with the methods of this embodiment resulting in the updated “count value” of “8” for the replica memory locations of machines M2 . . . Mn. How exactly the count value for each of the replica memory locations/addresses #15 has been changed or overwritten to indicate that a change in content has occurred, will now be explained.
Specifically, upon receipt of message 73, comprising an identifier of a replicated memory location(s), an associated updated value of the identified replicated memory location(s), and an associated contention value(s) (that is, a “count value” or a “logical sequence value”), such associated contention value(s) may be used to aid in the detection of a potential update conflict or inconsistency that may arise between two or more update messages for a same replicated memory location.
The use of the “count value” in accordance with the methods of this embodiment, allows the condition of conflicting or inconsistent updates for a same replicated memory location to be detected independently by each receiving machine of a plurality of machines. Specifically, the associating of a “count value” with a replicated memory location makes it possible to detect when two or more update transmissions relating to the same replicated memory location were transmitted by two or more machines without each transmitting machine knowing in advance of its transmission that another machine has (or is) similarly attempting to update the same replicated memory location. In otherwords, the association of a “count value” with a replicated memory location makes it possible to detect when two or more updates of two or more machines relating to a same replicated memory location, were transmitted without knowledge of one or more of the other update transmissions sent by some or all of the one or more other machines.
Such a problem arises due to the latency and delay of network communication through the network 53, where there is a latency/delay between transmission and receipt of a replica update transmission, and consequently such delay may be described as a “blind-spot” for a transmitting machine in that a first machine attempting a replica update transmission for a specific replicated memory location is not able to know at the time of transmission whether a second (or more) machine is also attempting a replica update transmission for the same specific replicated memory location at substantially the same time. Such a “blind spot” (or potential “contention window”) is illustrated in FIGS. 13, 14, 15, 16, 17 and 18.
Thus, through the use of a “count value” associated with a replicated memory location, where such “count value” indicates an approximate known update count of a replicated memory location by a transmitting machine, the occurrence of two or more update transmissions for a same replicated memory location sent by two or more machines, each transmitted substantially simultaneously/concurrently, is able to be detected, and thus the potential inconsistency and/or conflict that may arise from such plural transmissions may be detected.
How exactly “count value(s)” may be utilised during transmission of replica memory updates (comprising such “count value(s)”) to achieve this result, will now be described. Firstly, after a replicated memory location (such as memory location “A”) is updated, such as written-to, or modified, during operation of the application program of a first machine (such as machine M1), then the updated value of such written-to replicated memory location is signalled or queued to be updated to other corresponding replica memory locations of one or more other machines of the plurality, so that such corresponding replica memory locations, subject to a updating and transmission delay, will remain substantially similar.
Sometime after such replicated memory location “A” has been written-to, and preferably before the corresponding replica update transmission has taken place, the local/resident “count value” associated with the written-to replicated memory location (that is, the local copy of the “count value” on machine M1 associated with replicated memory location “A”) is incremented, and the incremented value is consequently stored to overwrite the previous local/resident “count value” (that is, the local/resident “count value” is incremented, and then overwritten with the incremented “count value”).
Either at substantially the same time as the “count value” is incremented, or at a later time, an updating transmission is prepared for the network 53. Such updating transmission preferably comprises three “contents” or “payloads” or “values”, that is a first content/payload/value identifying the written-to replicated memory location (for example, replicated memory location “A”), the second content/payload/value comprising the updated (changed) value of the written-to replicated memory location (that is, the current value(s) of the written-to replicated memory location), and finally the third content/payload/value comprising the incremented “count value” associated with the written-to replicated memory location.
Preferably, a single replica update transmission comprises all three “contents”, “payloads” or “values” in a single message, packet, cell, frame, or transmission, however this is not necessary and instead each of the three “contents”/“payloads”/“values” may be transmitted in two, three or more different messages, packets, cells, frames, or transmissions—such as each “content”/“payload”/“value” in a different transmission. Alternatively, two “contents”/“payloads”/“values” may be transmitted in a single first transmission and the third remaining “content”/“payload”/“values” in a second transmission. Further alternatively, other combinations or alternative multiple transmission and/or pairing/coupling arrangements of the three “contents”/“payloads”/“values” may be anticipated by one skilled in the computing arts, and are to be included within the scope of the present invention.
Importantly, the “count value” of a specific replicated memory location is incremented only once per replica update transmission of such replicated memory location, and not upon each occasion at which the specific replicated memory location is written-to by the application program of the local machine. Restated, the “count value” is only incremented upon occasion of a replica update transmission and not upon occasion of a write operation by the application program of the local machine to the associated replicated memory location. Consequently, regardless of how many times a replicated memory location is written-to by the application program of the local machine prior to a replica update transmission, the “count value” is only incremented once per replica update transmission. For example, where a replicated memory location is written-to 5 times by the application program of the local machine (such as by the application program executing a loop which writes to the same replicated memory location 5 times), but only a single replica update transmission of the last written-to value is transmitted (that is, the value of the 5th and last write operation), then the “count value” associated with the written-to replicated memory location is incremented once corresponding to the single replica update transmission.
How exactly the “count value” is utilised during receipt of replica update transmissions comprising a “count value” will now be described. The following steps upon receipt of a replica update transmission comprising an associated “count value”, are to take place on each receiving machine of the plurality of machines of a replicated shared memory arrangement on which a corresponding replica memory location resides. Importantly, the following steps are operable independently and autonomously by each machine (that is, are to preferably operate independently and autonomously by each receiving machine), such that no re-transmissions, conflict requests, or any other “resolving” or “correcting” or “detecting” transmissions between two or more machines are required or will take place in order to detect potentially conflicting transmissions. This is particularly advantageous as each receiving machine is therefore able to operate independently and autonomously of each other machine with respect to receiving and actioning replica memory updates comprising “count value(s)”, and detecting “conflicting”/“contending” transmissions.
Firstly, a replica updating transmission comprising an identity of a replicated memory location to be updated, the changed value to be used to update the corresponding replica memory locations of the other machine(s), and finally an associated “count value”, is received by a machine (for example, machine M2). Before the local corresponding replica memory location may be updated with the received changed value, the following steps must take place in order to ensure the consistent and “un-conflicted” updating of replica memory locations, and detect potentially “conflicting”/“contending” updates.
Firstly, the received associated “count value” is compared to the local/resident “count value” corresponding to the replica memory location to which the received replica update transmission relates. If the received “count value” of the received update transmission is greater than the local/resident “count value”, then the changed value of the received replica update transmission is deemed to be a “newer” value (that is, a more recent value) than the local/resident value of the local corresponding replica memory location. Consequently, it is desirable to update the local corresponding replica memory location with the received changed value. Thus, upon occasion of updating (overwriting) the local corresponding replica memory location with the received value, so too is the associated local “count value” also updated (overwritten) with the received “count value”. Such a first case as this is the most common case for replica memory update transmission, and represents an “un-conflicted”/“un-contended” (or as yet un-contended/un-conflicted) replica update transmission.
On the other hand, if the received “count value” of the received update transmission is less than the local/resident “count value”, then the changed value of the received replica update transmission is deemed to be an “older” value than the local/resident value of the local corresponding replica memory location. Consequently, it is not desirable to update the local corresponding replica memory location with the received changed value (as such value is a “stale” value), and as a result the received changed value may be disregarded or discarded.
However, a third condition is also possible—that is, where the received “count value” of the received transmission is equal to (the same as) the local/resident “count value”. When such a case as this occurs, the received changed value of the received replica update transmission can be neither guaranteed to be “newer”, nor “older” than the local/resident value of the local corresponding replica memory location. Consequently, when a condition such as this occurs (that is, the “count value” of a received replica update transmission is the same as the local/resident “count value” of the local corresponding replica memory location), then the received replica update transmission is deemed to be “in conflict” with the local corresponding replica memory location.
Such a potential “conflicting” condition between a received replica memory update and a local corresponding replica memory location will generally come about when two or more machines transmit a replica memory update for the same replicated memory location(s) at substantially the same time (that is, substantially simultaneously/concurrently). Such two or more transmissions are said to be “in contention”, as they conflict with each other, and if not detected to be “in contention” (that is, in conflict), then there is a risk that the multiple corresponding replica memory locations of the effected replicated memory location (that is, the replicated memory location to which the contending/conflicting updating transmissions relate) will not be updated by the plural machines in a consistent and coherent manner. Such an example of substantially simultaneous/concurrent updating by two or more machines of a same replicated memory location resulting in inconsistent updating of replica memory locations of the plural machines is illustrated in FIGS. 6-7 and 15.
For example, upon occasion of two replica update transmission for the same replicated memory location occurring (being transmitted) substantially simultaneously/concurrently, and each transmitted with the same associated “count value”, then by utilising the abovedescribed methods it is possible for each receiving machine to independently detect such “conflicting” transmission independently (that is without the aid of) any other machine, and without requiring any additional transmissions by either the receiving or sending machine(s). Furthermore, each receiving machine is able to detect such “conflicting” transmissions regardless of the order in which they arrive at the receiving machine (and potentially in differing orders for different receiving machines).
Additionally, the abovedescribed methods also facilitate the detecting of conflicting transmissions by each of the sending machines. That is, for each of the plural conflicting sending machines, each one of such sending machines is able to similarly independently detect the conflicting replica memory updates of each other transmitting machine upon occasion of the receipt of each such update(s), and without requiring any additional transmissions by either the receiving or sending machine(s).
Furthermore again, the abovedescribed methods achieve the desired aim of being able to detect contending/conflicting replica update transmissions without requiring re-transmissions by one, some, or all of the transmitting machines of the effected (that is, conflicting) transmissions.
Thus, the abovedescribed methods disclose a system of transmitting replica memory updates in such a manner in which consideration or allowance or special handling or other special steps (such as acquiring exclusive update permission for a replicated memory location) during transmission for preventing potentially conflicting transmissions by other machines, is not required. In otherwords, the abovedescribed use of associated “count value(s)” with replicated memory locations, makes it possible to transmit “self-contained” replica memory updates to all receiving machines, where the values/information of such “self-contained” replica memory updates comprise all the necessary information to facilitate the detection of potential conflicting transmission (for a same replicated memory location) unknown to the transmitting machine at the time of transmission. Importantly, such “self-contained” replica memory updates comprising “count values”, may be transmitted by a sending machine without regard for potentially conflicting transmissions by one or more other machines, as such “self-contained” replica update transmissions (including “count values”) contain all the necessary information to facilitate the detection of conflicting updates of other machines for the same replicated memory location.
Consequently, each transmitting machine is able to operate independently and unfettered, and without requiring any “transmission authorization”, transmission permissions (such as exclusive transmission permissions), exclusive update or write permissions or the like, and instead each transmitting machine (and each potentially simultaneously transmitting machine) may transmit replica memory updates whenever and however it chooses without regard for potential conflicting transmissions of other machines as the use of the abovedescribed methods are able to detect such potential conflicting transmissions on each receiving machine independently of each other machine.
Thus, it will be appreciated by the reader, that the abovedescribed methods for replica update transmission (comprising “count values”) achieves a desired operating arrangement which allows the transmission of a single replica memory update transmission (such as a single message, cell, frame, packet, or other transmission unit) by a first transmitting machine whether or not such single transmission will ultimately “conflict” or contend with one or more other transmissions of one or more other machines. As a result, through the use of “count values” as described above, transmitting machines may transmit single or plural replica memory updates at any time, and for any replicated memory location, to any one or more other machines regardless of whether or not such replica memory updates will or may conflict or contend with one or more other transmissions of one or more other machines.
Furthermore, it will be appreciated by the reader that the abovedescribed methods for replica update transmission (comprising “count values”) achieves an additional desired operating arrangement in which re-transmissions, re-tried transmissions, stalled transmissions or the like do not result from a condition of two or more update transmissions contending/conflicting.
Furthermore again, the abovedescribed methods for replica update transmission achieves a further desired operating arrangement/result in which, upon occasion of two or more conflicting replica update transmissions (such as a first replica update transmission of machine M1 for replicated memory location “A”, and a conflicting second replica update transmission of machine M2 for the same replicated memory location “A”), that further ongoing replica update transmissions by machines M1 and M2 for either or both of the same replicated memory location “A”, or any other replicated memory location(s), may continue in an uninterrupted and unhindered manner—specifically, without causing further/later replica memory update transmissions (including further/later update transmissions of replicated memory location “A”) following such “conflicting” transmission(s) to be stalled, interrupted or delayed.
Furthermore again, the abovedescribed methods for replica update transmission achieves a further desired operating arrangement/result in which, upon occasion of two or more conflicting replica update transmissions (such as a first replica update transmission of machine M1 for replicated memory location “A”, and a conflicting second replica update transmissions for machine M2 for the same replicated memory location “A”), will not effect the replica memory update transmissions of any other machine (for example, machines M3 . . . Mn) whether such other transmissions apply/relate to replicated memory location “A” or not. Thus, transmissions of other machines (for example, machines M3 . . . Mn) are able to also proceed and take place in an uninterrupted, unhindered and unfettered manner in the presence of (for example, substantially simultaneously to) two or more conflicting transmissions (such as of machines M1 and M2), even when such other transmissions of machines M3 . . . Mn relate/apply to replicated memory location “A”.
Thus, the abovedescribed methods of detecting potentially conflicting or contending replica update transmissions addresses the detection of contention.
Altogether, the operation of a multiple computer system comprising transmitting and receiving machines, and utilising the abovedescribed “count value” to detect conflicting updates, will now be explained.
Turning now to FIG. 16, the example of FIGS. 9-10 is collectively illustrated in a time-diagram. Here, machine M1 transmits replica memory update N401 (which corresponds to replica update 73 of FIGS. 9 and 10) at time-unit 1, with the updated value “211” of address #15 and the contention value (“count value”) of “8”, to machines M2, M3 . . . Mn on which corresponding replica memory locations reside.
Corresponding to transmission N401 by machine M1, in accordance with the abovedescribed rules the “count value” of machine M1 of the updated replicated memory location/address #15 is incremented by 1 to become “8” (that is, the resident “count value” of “7” is incremented to become the new “count value” of “8”). Replica memory update N401 is then transmitted to machines M2-Mn, comprising the updated value “211” of the written-to replicated memory location of machine M1 (that is, replicated memory location/address #15), the identity of the replicated memory location to which the updated value corresponds (that is, replicated memory location/address #15), and the associated incremented “count value” of the replicated memory location to which the updated value corresponds (that is, the new resident “count value” of “8”).
However, as is indicated in FIG. 16, transmission N401 does not arrive at the receiving machines M2-Mn immediately (that is, at the same time-unit 1 of transmission). Instead, each receiving machine is indicated to receive replica update transmission N401 at time-unit 5 by the arrows shown for each machine M2-Mn. Thus, FIG. 16 illustrates a time-delay N410 that typically results between transmission and receipt of a replica memory update, due to latency and delay of the communications network used to interconnect and transmit the replica memory updates between the multiple computers of the multiple computer system. This period of delay, N410, represents the “transmission latency/delay” between the sending or replica update transmission N401 by machine M1, and the receipt of the same replica update transmission N401 by machines M2-Mn.
Following transmission N401 by machine M1, the receiving machines M2-Mn each independently receive the transmission N401, and proceed to independently “action” the received transmission according to the abovedescribed rules. Specifically, by comparing the “count value” of the received transmission N401 with the resident (local) “count value” of the corresponding replica memory location of each receiving machine (which is indicated to be “7” for all machines), it is able to be determined that the received “count value” of transmission N401 (that is, the count value “8”) is greater than the resident “count value” of the corresponding replica memory location of each machine (that is, the resident count value “7”).
As a result, the determination is made that the received updated value of transmission N401 is a newer value than the resident value of machines M2-Mn, and therefore receiving machines M2-Mn are permitted to update their local corresponding replica memory locations with the received updated replica value. Accordingly then, each receiving machine M2-Mn replaces the resident (local) “count value” of the local corresponding replica memory location with the received “count value” of transmission N401 (that is, overwrites the resident “count value” of “7” with the received “count value” of “8”), and updates the local corresponding replica memory location with the received updated replica memory location value (that is, overwrites the previous value “107” with the received value “211”).
Thus, the use of the “count value” as described, allows a determination to be made at the receiving machines M2-Mn that the transmitted replica update N401 of machine M1 is newer than the local resident value of each receiving machine. Therefore, machines M2-Mn are able to be successfully updated in a consistent and coherent manner with the updated replica value of transmission N401, and the aim of consistent and coherent updating of replicated memory location(s) is achieved.
For example, consider FIG. 17. FIG. 17 follows on from FIG. 16, where at time-unit 7, and following receipt of transmission N401, machine M3 transmits replica memory update N402, with the updated value “999” of address #15 and the updated “count value” of “9”, to machines M1, M2, M4 . . . Mn. Specifically, the additional transmissions N402 by machine M3 to machines M1, M2, M4 . . . Mn is a transmission of an updated replica value generated by the operation of machine M3 for the same replicated memory location updated by transmission N401 (that is, replicated memory location/address #15).
Corresponding to transmission N402 by machine M3, in accordance with the abovedescribed rules the “count value” of machine M3 of the updated replicated memory location/address #15 is incremented by 1 to become “9” (that is, the resident “count value” of “8” is incremented to become the new “count value” of “9”). Replica memory update N402 is then transmitted to machines M1, M2, M4 . . . Mn, comprising the updated value “999” of the written-to replicated memory location of machine M3 (that is, replicated memory location/address #15), the identity of the replicated memory location to which the updated value corresponds (that is, replicated memory location/address #15), and the associated incremented “count value” of the replicated memory location to which the updated value corresponds (that is, the new resident “count value” of “9”).
Next, at time-unit 11 is indicated that machines M1, M2, M4 . . . Mn receive transmission N402, and proceed to independently “action” the received transmission according to abovedescribed rules in a similar manner to the actioning of the received transmission N401 by machines M2-Mn. Specifically, by comparing the “count value” of the received transmission N402 with the resident (local) “count value” of the corresponding replica memory location of each receiving machine (which is indicated to be “8” for all machines), it is able to be determined that the received “count value” of transmission N402 (that is, the count value “9”) is greater than the resident “count value” of the corresponding replica memory location of each machine (that is, the resident count value “8”).
As a result, the determination is made that the received updated value of transmission N402 is a newer value than the resident value of machines M1, M2, M4-Mn, and therefore machines M1, M2, M4-Mn are permitted to update their local corresponding replica memory locations with the received updated replica value. Accordingly then, each receiving machine M1, M2, M4-Mn replaces the resident (local) “count value” of the local corresponding replica memory location with the received “count value” of transmission N402 (that is, overwrites the resident “count value” of “8” with the received “count value” of “9”), and updates the local corresponding replica memory location with the received updated replica memory location value (that is, overwrites the previous value “211” with the received value “999”).
Thus, the use of the “count value” as described, allows a determination to be made at the receiving machines M1, M2, M4 . . . Mn that the transmitted replica update N402 of machine M3 is newer than the local resident value of each receiving machine. Therefore, machines M1, M2, M4 . . . Mn are able to be successfully updated in a consistent and coherent manner with the updated replica value of transmission N402, and the aim of consistent and coherent updating of replicated memory location(s) is achieved.
Critically, what is accomplished through the use of an associated “count value” for each replica memory location (or set of replica memory locations), is that such “count value” may be used to signal when a replica update is newer or older (or neither newer nor older) than a replica memory location value already resident on a receiving machine. As can be seen in FIGS. 16 and 17, the first transmission N401 of machine M1 has a count value of “8”, which is subsequently received by machines M2-Mn. Some time subsequent to the receipt of transmission N401 by machine M3 (e.g. time-unit 7), machine M3 transmits a replica update of a new value for the same replicated memory location of transmission N401 (that is, replicated memory location/address #15), and consequently associates with such transmission N402 a new “count value” of “9”, indicating that such transmission N402 is “newer” (or “later”) than transmission N401 (which had a “count value” of “8”).
As a result, by using the abovedescribed methods, it is able to be ensured that for example were transmission N401 to be received by a machine (such as machine M2) after receipt of transmission N402 by the same machine (e.g. machine M2), that the “late” received transmission N401 would not cause the replica memory location value of machine M2 (in which is stored the value of the previously received transmission N402) to be overwritten with the “older” (or “earlier”) value of transmission N401. This is because, in accordance with abovedescribed operation of “count values”, the resident “count value” of machine M2 for replicated memory location/address #15 after receipt of transmission N402 would have been overwritten to become “9”. Therefore upon receiving transmission N401 with a “count value” of “8” after receipt and actioning of transmission N402, in accordance with the abovedescribed “count value” rules, such received transmission N401 would not cause the local replica memory location #15 of machine M2 to be updated with the received updated value of transmission N401 as the “count value” of transmission N401 would be less than the resident “count value” of “9” resulting from the previous receipt and actioning of transmission N402. Thus, consistent and coherent replica updating is achieved.
FIG. 11 illustrates what happens in the circumstance discussed above in relation to FIG. 6 where two (or more) machines M1 and M3 simultaneously, or substantially simultaneously, update the same replicated memory location/address. As in FIG. 10, machine M1 in executing its portion of the application program causes the contents of replicated memory location/address #15 to be written with a new content “211”. As a result, the “count value” associated with replicated memory location/address #15 is incremented from “7” to “8”, and message 73 is sent via the network 53 to all other machines M2, M3, . . . Mn comprising the updated value of replicated memory location/address #15 (that is, “211”), the identity of the written-to replicated memory location (that is, address #15), and the associated incremented “count value” (that is, “8”). Substantially simultaneously, machine M3 in executing its portion of the application program writes a new content “92” to the same replicated memory location/address #15, and as a result similarly increments its “count value” from “7” to “8” and sends a message 74 containing these particulars (that is, the identity of the written-to replicated memory location, the updated value of the written-to replicated memory location, and the associated incremented “count value”) to all other machines M1, M2, M4, M5, . . . Mn. This is the situation illustrated in FIG. 11.
The consequence of the situation illustrated in FIG. 11 is illustrated in FIG. 12. As in FIG. 7, machines M2, M4, M5 . . . Mn which did not initiate any/either message will have received a first one of either messages 73 or 74 (in either order), and proceed to “action” such first received transmission in accordance with the abovedescribed methods. Specifically, regardless of whether message 73 or 74 is received first, such first received message will cause the updating of the local corresponding replica memory location, as such first received message will have a “count value” of “8” which is greater than the resident “count value” of “7” for each of the receiving machines (that is, the value of the first received transmission is deemed newer than current value of the local corresponding replica memory location). Therefore, in actioning the first received message/transmission, the resident “count value” will be caused to be overwritten from “7” to “8”, and the local corresponding replica memory location will be update/replaced (e.g. overwritten) with the received updated value of the first received transmission. Consequently, following such actioning of the first received transmission, the content stored (or overwritten) at the local memory corresponding to replicated memory location/address #15 will be either 211 or 92 depending upon which one of messages 73 or 74 is received first, and the associated local/resident “count value” will be “8”.
However, upon occasion of each receiving machine M2, M4, M5 . . . Mn receiving the second of the two transmissions/messages 73 and 74, and proceeding to “action” such second received transmission in accordance with the abovedescribed methods, a condition of “conflict”/“contention” will be detected between the “count value” of the second received transmission and the corresponding local/resident “count value”. Specifically, in actioning the second received message/transmission, a comparison of the resident “count value” (with a value of “8”), and the “count value” of the second received transmission (also with a value of “8”), will result in a determination that the second received transmission “conflicts”/“contends” with the resident “count value”. Therefore, upon receipt and actioning of the second received transmission/message, each receiving machine M2, M4, M5 . . . Mn is able to detect and signal a condition of “conflict” between the first and second received transmissions, by detecting a “conflict” between the updated resident “count value” resulting from the actioning of the first received transmission, and the “count value” of the second received transmission (both values of which are identical).
It will thus be appreciated that the machines M2, M4, M5, . . . Mn having received the first one of messages 73 and 74 and thereby having an updated “count value” of “8” (resulting from the actioning of such first received message), when they receive the second of the messages 73 and 74 will have a resident “count value” which is the same as the “count value” of the second received message. Thus these machines can detect and signal contention.
However, for machines M1 and M3, each of which transmits message 73 and 74 respectively, only a single message will be received (that is, the other one of the two transmitted messages 73 and 74). Specifically, in accordance with the abovedescribed methods, upon occasion of transmission of messages 73 and 74 by machines M1 and M3 respectively, each transmitting machine increments the local/resident “count value” for replicated memory location/address #15 (for example, from a value of “7” to a value of “8”) and stores the incremented count value to overwrite/replace the previous resident “count value”, and also transmits the incremented “count value” within (or otherwise a part of or associated with) message 73 and 74 respectively. Thus, upon transmission of messages 73 and 74 by machines M1 and M3 respectively, each transmitting machine (that is, machines M1 and M3) will each have a local/resident “count value” of “8” for replicated memory location/address #15 corresponding to the transmission of replica memory update message 73 and 74 respectively.
Thus by comparing the resident “count value” with the received “count value” of message 74 (by means of a comparator, for example) machine M1 is able to detect and signal that a “conflict”/“contention” situation has arisen because it detects the situation where the incoming message 74 contains a “count value” (that is, a “count value” of “8”) which is identical to the existing state of the resident “count value” associated with replicated memory location/address #15 (which is also a “count value” of “8”).
Similarly, machine M3 on receipt of message 73 also receives an incoming message with the same “count value” as the corresponding resident “count value”. Thus, machine M3 is also able to detect and signal that a “conflict”/“contention” situation has arisen because it detects the situation where the incoming message 73 contains a “count value” (that is, a “count value” of “8”) which is identical to the existing state of the resident “count value” associated with replicated memory location/address #15 (which is also a “count value” of “8”).
It will thus be appreciated that the two transmitting machines M1 and M3 having transmitted messages 73 and 74 respectively, and thereby having an incremented “count value” of “8” (resulting from the transmission of the respective one of messages 73 and 74), when they receive message 74 and 73 respectively will have a resident “count value” which is the same as the “count value” of the received message. Thus these machines too can detect and signal contention.
Turning thus to FIG. 18, the example of FIGS. 11-12 is collectively illustrated in a time-diagram. Here, machine M1 transmits replica memory update N601 (which corresponds to replica update 73 of FIGS. 11 and 12), with the updated value “211” of address #15 and the contention value (“count value”) of “8”, to machines M2, M3 . . . Mn on which corresponding replica memory locations reside. Also, substantially simultaneously/concurrently machine M3 also transmits a replica memory update N602 (which corresponds to replica update 74 of FIGS. 11 and 12), with the updated value “92” of the same address #15 and the contention value (“count value”) of “8”, to machines M1, M2, M4 . . . Mn on which corresponding replica memory locations reside.
Also, as is indicated in FIG. 18, transmissions N601 and N602 do not arrive at the receiving machines immediately (that is, at the same time-unit 1 of transmission). Instead, each receiving machine is indicated to receive replica update transmissions N601 and N602 at time-unit 5 by the arrows shown for each machine M1-Mn.
However, unlike the case of FIGS. 6 and 7, the use of the associated “count values” for transmissions N601 and N602, together with the resident “count values” of each receiving machine, is able to detect the two conflicting/contending replica update transmissions N601 and N602. Specifically, regardless of which replica update transmission N601 or N602 is received first by machines M2, M4 . . . Mn, each machine will independently be able to detect that the second of the two received transmissions conflicts/contends with the first received transmission.
Furthermore, each transmitting machine M1 and M3, will independently be able to detect that the received transmission of the other machine conflicts/contends with the local value of the receiving machine.
Thus, by using the abovedescribed methods to associate “count value(s)” with replicated memory location(s), and by using the rules described herein for the operation and comparison of such “count value(s)”, consistent updating of replica memory locations of plural machines may be achieved, and detection of conflicting/contending replica update transmissions may also achieved.
Thus it will be seen from the above example that the provision of the “count value(s)” in conjunction/association with replicated memory location(s) provides a means by which contention can be detected, and consistent updating of replicated memory locations be achieved/ensured. This is a first step in ensuring that the replicated memory structure remains consistent.
Thus the provision of the “count value” and the provision of a simple rule, namely that incoming messages with updating content of a replicated memory location are valid if the resident “count value” is less than the received “count value”, but are in “conflict” if the two “count values” are the same, enables a state of “conflict”/“contention” to be detected.
Thus, as illustrated in FIGS. 11-12 and 18, when two replica update messages/transmissions are received with the same “count value” from different machines, then it is able to be known/determined that such two update messages were sent by each different sending machine prior receipt of the other sending machine's corresponding update message. As a result, the two messages are detected to contend (or be in conflict), because there is the potential for inconsistency to result or arise amongst or between the receiving and/or sending machines of the plurality if such conflicting transmission(s)/message(s) are updated to local memory (such as occurred in the case of FIG. 7).
Additionally is conceived a preferred further improved arrangement of storing “count values” corresponding to replicated memory locations. Specifically, it is envisaged of preferably storing “count vales” in such a manner so as to be inaccessible by the application program such as by the application program code. FIG. 19 describes this further preferred storage arrangement.
FIG. 19 depicts a single machine M1 of the plurality of machines depicted in FIG. 2. The other machines (M2-M4) have been omitted from this figure for simplicity of illustration, though the depiction of the preferred storage arrangement of FIG. 19 is applicable to all such machines of such a plurality (such as machines M2-Mn of FIG. 2), as well as any other replicated, distributed, or multiple computer system arrangement.
Specifically, indicated in FIG. 19 is the memory of machine M1 in which is indicated a non-application memory region N701, indicated as a dotted square. Such memory is preferably inaccessible to the application program executing on machine M1, in contrast to memory locations A, B and C, and the dotted outline is used in this drawing to indicate this and differentiate it from the accessible memory locations A, B and C.
In the preferred arrangement depicted in FIG. 19, the “count value(s)” are stored in such a non-application memory region, so as to be inaccessible to the application program and application program code.
Various memory arrangements and methods for non-application-accessible memory regions is know in the prior art, such as using virtual memory, pages, and memory management units (MMUs) to create memory spaces or regions or address-ranges inaccessible to specific instructions or code (such as for example application program code). Other arrangements are also known in the prior art, such as through the use of namespaces, software or application domains, virtual machines, and segregated/independent memory heaps, and all such memory partitioning, segregation and/or memory access-control methods and arrangements are to be included within the scope of the present invention.
Such an arrangement is preferable so that the “count values” stored in the non-application memory region N701 are not able to be tampered with, edited, manipulated, modified, destroyed, deleted or otherwise interfered with by the application program or application program code in an unauthorized, unintended, unexpected or unsupported manner.
Though only a single non-application memory region is indicated in FIG. 19, more than one non-application memory region may be used, and any such multi-region arrangement is to be considered included within the scope of the present invention.
In at least one embodiment of this invention, one, some, or all “count value(s)” of a single machine, may be stored in internal memory, main memory, system memory, real-memory, virtual-memory, volatile memory, cache memory, or any other primary storage or other memory/storage of such single machine as may be directly accessed (or accessible) to/by the central processing unit(s) of the single machine.
Alternatively, in at least one further alternative embodiment of this invention, one, some, or all “count value(s)” of a single machine, may be stored in external memory, flash memory, non-volatile memory, or any other secondary storage or other memory/storage of such single machine as may not be directly accessed (or accessible) to/by the central processing unit(s) of the single machine (such as for example, magnetic or optical disk drives, tape drives, flash drives, or the like).
Alternatively again, in at least one further alternative embodiment of this invention, some first subset of all “count value(s)” of a single machine may be stored in internal memory, main memory, system memory, real-memory, virtual-memory, volatile memory, cache memory, or any other primary storage or other memory/storage of such single machine as may be directly accessed (or accessible) to/by the central processing unit(s) of the single machine, and some other second subset of all “count value(s)” of the single machine may be stored in external memory, flash memory, non-volatile memory, or any other secondary storage or other memory/storage of such single machine as may not be directly accessed (or accessible) to/by the central processing unit(s) of the single machine (such as for example, magnetic or optical disk drives, tape drives, flash drives, or the like). Further alternatively again, in at least one further alternative embodiment of this invention, “count value(s)” of such first subset and such second subset may be moved between/amongst (e.g. moved from or to) such first and second subsets, and thereby also moved between/amongst (e.g. moved from or to) such internal memory (e.g. primary storage) and such external memory (e.g. secondary storage).
Importantly, the above-described method of actioning replica update messages having a “count value” associated with an updated value of a replicated memory location, makes possible the detection, or the ability to detect, the occurrence of two or more conflicting replica update messages for a same replicated memory location. Furthermore, such “actioning” of received replica update messages by each receiving machine may occur independently of each other machine (and potentially at different times and/or different orders on different machines), and without additional communication, confirmation, acknowledgement or other communications of or between such machines to achieve the actioning of each received transmission.
For a plurality of corresponding replica memory locations of a plurality of machines (one of each corresponding replica memory locations on each one of such machines), there is only a single “count value”, and not multiple “per-machine” count-values—such as for example, a unique “count value” of machine M1 for replica memory location A, and a second and different “count value” of machine M2 for replica memory location A. As a result, each machine does not need to store multiple “count values” for a single replica memory location (such as for example machine M1 storing a copy of machine M1's “count value” for replica memory location A, as well as storing a local copy of machine M2's “count value” for replica memory location A, as well as storing a local copy of machine M3's “count value” for replica memory location A etc.), nor transmit with each replica update transmission more than one “count value” for a single replica memory location. Consequently, as the number of machines comprising the plurality grows, there is not a corresponding growth of plural “count values” of a single replicated memory location required to be maintained. Specifically, only one “count value” is maintained for all corresponding replica memory locations of all machines, and not one “count value” for each machine on which a corresponding replica memory location resides. Therefore, as the number of machines in the plurality grows, there is not a growth of per-machine “count-values” for replicated memory locations.
Alternative associations and correspondences between “count value(s)” and replicated memory location(s) are also provided. Specifically, in addition to the above described “one-to-one” association of a single “count value” with each single replicated memory location, alternative arrangements are provided where a single “count value” may be associated with two or more replicated memory locations. For example, a single “count value” may be stored and/or transmitted for a related set of replicated memory locations, such as plural replicated memory locations comprising an array data structure, or an object, or a class, or a “struct”, or a virtual memory page, or other structured data type comprising two or more related and/or associated replicated memory locations.
Preferably, “count value(s)” are not stored and/or operated for non-replicated memory locations or non-replica memory locations (that is, memory location(s) which are not replicated on two or machines and updated to remain substantially similar). Consequently, “count values” are preferably not stored for such non-replicated memory locations and/or non-replica memory locations.
Also preferably, “count value(s)” corresponding to a specific replicated memory location (or set of replicated memory location(s)) are only stored and/or operated on those machines on which such specific replicated memory location is replicated (that is, on those machines on which a corresponding local replica memory location resides).
Preferably, when a replicated memory location which is replicated on some number of machines (such as for example machines M1-M3), is additionally replicated on a further machine (such as a machine M4), then a local/resident “count value” is created on such further machine (e.g. machine M4) corresponding to such additionally replicated memory location, and initialised with a substantially similar value of at least one of the “count value(s)” of the other machines on which the additionally replicated memory location was already replicated (e.g. machines M1-M3). Preferably, such process of creating and initialising a “count value” on such further machine (e.g. machine M4) does not cause the “count value(s)” of any other machine (e.g. machines M1-M3) to be incremented, updated or changed. Thereafter, replica update transmissions may be sent and received by all machines (including the further machine on which the replicated memory location was additionally replicated) on which a corresponding replica memory location resides (e.g. machines M1-M4), in accordance with the above-described methods and arrangements.
Preferably, when a non-replicated memory location of a first machine (such as for example machine M1), is replicated on one or more further machines (such as a machines M2-M4), then a local/resident “count value” is created corresponding to such replicated memory location on both of such first machine (e.g. machine M1) and such further machines (e.g. machines M2-M4), and initialised with a substantially similar initial value. Preferably such initial value is zero (ie “0”), however any other alternative initial values may be used so long as such alternative initial value is substantially similar across all such corresponding resident “count values” of all machines (e.g. machines M1-M4). Preferably also, such process of creating and initialising a “count value” on such first machine (e.g. machine M1) and such further machines (e.g. machines M2-M4) does not cause the initial “count value(s)” to be incremented, updated or changed. Thereafter, replica update transmissions may be sent and received by all machines (including the first machine and further machine(s)) on which a corresponding replica memory location resides (e.g. machines M1-M4), in accordance with the above-described methods and arrangements.
To summarize, there is disclosed a method of detecting contention in addressed memory updating in which a memory location having a specific location identifier can be updated substantially simultaneously from a plurality of sources, the method comprising the steps of:

    (i) utilizing an updating format for the signal or packet carrying out the updating, the format comprising the specific identifier of the memory location to be updated, the content with which the memory location is to be updated, and a resident updating count of the updating source, the count comprising a number indicative of the position of the updating message in the sequence of occasions on which the updating source has been updated inclusive of the current updating,
    (ii) storing for each receiving memory location the updating count of the previously received updating,
    (iii) comparing the updating count presently resident at the receiving memory location with the updating count of any currently received updating signal or packet, and
    (iv) indicating a contention situation if the compared updating counts are the same.


Preferably the method includes the further step of:

    (v) incrementing the resident updating count of the updating source on each occasion on which the updating source is locally updated.


Preferably the method includes the further step of:

    (vi) incrementing the updating source resident updating count by one.


Preferably the memory location is one of a plurality of memory locations resident in one of a plurality of computers and each of the plurality of computers has substantially the same structure of memory locations.
Preferably each the updatable memory location in one of the computers has a corresponding memory location in each of the others of the computers.
Preferably each the updatable memory location has a local memory address which is different from the location identifier.
There is also disclosed a system for detecting contention in addressed memory updating, the system comprising at least one memory location having a specific location identifier; a plurality of sources each of which can update the memory location(s) and each of which utilizes an updating format for the signal or packet carrying out the updating, the format comprising the specific identifier of the memory location to be updated, the content with which the memory location is to be updated, and a resident updating count of the updating source, the count comprising a number indicative of the position of the updating message in the sequence of occasions on which the updating source has been updated inclusive of the current updating; a storage means associated with each the memory location and in which the updating count of the previously received updating is stored; comparison means to compare the previously stored updating count with the updating count of any currently received updating signal or packet; and contention indicating means connected with the comparison means and operable to indicate a contention situation if the compared updating counts are the same.
Preferably the method includes incrementing means to increment the resident updating count of the updating source on each occasion on which the updating source is locally updated.
Preferably the incrementing means increments the resident updating count by one.
Preferably the memory location is one of a plurality of memory locations resident in one of a plurality of computers and each of the plurality of computers has substantially the same structure of memory locations.
Preferably each the updatable memory location in one of the computers has a corresponding memory location in each of the others of the computers.
Preferably each the updatable memory location has a local memory address which is different from the location identifier.
In addition, there is also disclosed in a multiple computer system comprising a multiplicity of computers, each interconnected via at least one communications network, and each executing a different portion of an applications program written to execute on a single computer and, each having an independent local memory with at least one memory location being replicated in each the local memory, and a method of detecting contention in replica memory updating in which a memory location having a specific location identifier and replicated on at least two of the computers, can be updated substantially simultaneously from a plurality of sources, the method comprising the steps of:

    (i) utilizing an updating format for the signal or packet carrying out the updating, the format comprising the specific identifier of the memory location to be updated, the content with which the memory location is to be updated, and a resident updating count of the updating source, the count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating,
    (ii) storing for each replicated memory location the updating count of the previously sent or received updating,
    (iii) comparing the resident updating count associated with the replicated memory location to be updated with the updating count of the currently received updating signal or packet, and
    (iv) indicating a contention situation if the compared updating counts are the same.


Furthermore there is also disclosed a multiple computer system comprising a multiplicity of computers, each interconnected via at least one communications network, and each executing a different portion of an applications program written to execute on a single computer, and each having an independent local memory with at least one memory location being replicated in each the local memory, and a detection means for detecting contention in replica memory updating, the detection means comprising at least one memory location having a specific location identifier and replicated on at least two machines, and updated to remain substantially similar upon occasion of a machine modifying its replica value; a plurality of sources each of which can update the memory location(s) and each of which utilizes an updating format for the signal or packet carrying out the updating, the format comprising the specific identifier of the memory location to be updated, the content with which the memory location is to be updated, and a resident updating count of the updating source, the count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating; a storage means associated with each the memory location and in which the updating count of the previously received updating is stored; comparison means to compare the previously stored updating count with the updating count of the currently received updating signal or packet; and contention indicating means connected with the comparison means and operable to indicate a contention situation if the compared updating counts are the same.
Still further, there is disclosed a multiple computer system comprising a multiplicity of computers, each interconnected via at least one communications network, and each executing a different portion of an applications program written to execute on a single computer, each having an independent local memory with at least one memory location being replicated in each the local memory, a method of replica memory updating in which a memory location having a specific location identifier and replicated on at least two computers, can be updated substantially simultaneously from a plurality of sources, the method comprising the steps of:

    (i) utilizing an updating format for the signal or packet carrying out the updating, the format comprising the specific identifier of the memory location to be updated, the content with which the memory location is to be updated, and a resident updating count of the updating source, the count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating,
    (ii) storing for each replicated memory location the updating count of the previously sent or received updating,
    (iii) comparing the presently resident updating count associated with the replicated memory location to be updated with the updating count of the currently received updating signal or packet, and
    (iv) if the currently received updating count is greater than the presently resident updating count, overwriting the associated replicated memory location with the currently received data content, and overwriting the presently resident updating count with the currently received updating count, or
    (v) if the currently received updating count is less than the presently resident updating count, not overwriting the associated replicated memory location with the currently received data content, and not overwriting the presently resident updating count with the currently received updating count, or
    (vi) if the currently received updating count is equal to the presently resident updating count, indicating a contention situation.


Still further yet, there is disclosed a multiple computer system comprising a multiplicity of computers, each interconnected via at least one communications network, and each executing a different portion of an applications program written to execute on a single computer, and each having an independent local memory with at least one memory location being replicated in each the local memory, and an updating for replica memory updating, the updating means comprising at least one memory location having a specific location identifier and replicated on at least two machines, and updated to remain substantially similar upon occasion of a machine modifying its replica value; a plurality of sources each of which can update the memory location(s) and each of which utilizes an updating format for the signal or packet carrying out the updating, the format comprising the specific identifier of the memory location to be updated, the content with which the memory location is to be updated, and a resident updating count of the updating source, the count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating; a storage means associated with each the memory location and in which the updating count of the previously received updating is stored; comparison means to compare the currently received updating count value with the presently resident updating count value and overwriting the associated replicated memory location with the currently received data content and overwriting the presently resident updating count with the currently received updating count, if the currently received updating count exceeds the presently resident updating count, or not overwriting the associated replicated memory location with the currently received data content and not overwriting the presently resident updating count with the currently received updating count, if the currently received updating count is less than the presently resident updating count; and contention indicating means connected with the comparison means and operable to indicate a contention situation if the compared updating counts are the same. Preferably the count comparison means is a comparator.
Finally, there is disclosed an a single computer for use in cooperation with at least one other computer in a multiple computer system, wherein the multiple computer system comprising a multiplicity of computers, each interconnected via at least one communications network, and each executing a different portion of an applications program written to execute on a single computer, each having an independent local memory with at least one memory location being replicated in each the local memory, a method of replica memory updating in which a memory location having a specific location identifier and replicated on at least two computers, can be updated substantially simultaneously from a plurality of sources, the method comprising the steps of:

    (i) utilizing an updating format for the signal or packet carrying out the updating, the format comprising the specific identifier of the memory location to be updated, the content with which the memory location is to be updated, and a resident updating count of the updating source, the count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating,
    (ii) storing for each replicated memory location the updating count of the previously sent or received updating,
    (iii) comparing the presently resident updating count associated with the replicated memory location to be updated with the updating count of the currently received updating signal or packet, and
    (iv) if the currently received updating count is greater than the presently resident updating count, overwriting the associated replicated memory location with the currently received data content, and overwriting the presently resident updating count with the currently received updating count, or
    (v) if the currently received updating count is less than the presently resident updating count, not overwriting the associated replicated memory location with the currently received data content, and not overwriting the presently resident updating count with the currently received updating count, or
    (vi) if the currently received updating count is equal to the presently resident updating count, indicating a contention situation.


The foregoing describes only some embodiments of the present invention and modifications, obvious to those skilled in the computing arts, can be made thereto without departing from the scope of the present invention. For example, reference to JAVA includes both the JAVA language and also JAVA platform and architecture.
Similarly, the “count values” described above are integers but this need not be the case. Fractional “count values” (i.e. using a float or floating point arithmetic or decimal fraction) are possible but are undesirably complex.
It will also be appreciated to those skilled in the art that rather than incrementing the “count value” for successive messages, the “count value” could be decremented instead. This would result in later messages being identified by lower “count values” rather than higher “count values” as described above.
In the various embodiments of the present invention described above, local/resident “count value(s)” of written-to replicated memory location(s) are described to be incremented by a value of “1” prior to, or upon occasion of, a replica update transmission by a sending machine being transmitted. Such incremented “count value” is also described to be stored to overwrite/replace the previous local/resident “count value” of the transmitting machine (e.g. that is, the local/resident “count value” from the which the incremented “count value” was calculated). However, it is not a requirement of the present invention that such incremented “count values” must be incremented by a value of “1”. Instead, alternative arrangements of the present invention are anticipated where such incremented “count value(s)” may be (or have been) incremented by a value of more than “1” (for example, “2”, or “10”, or “100”). Specifically, exactly what increment value is chosen to be employed to increment a “count value” is not important for this invention, so long as the resulting “incremented count value” is greater than the previous local/resident “count value”.
Furthermore, alternative arrangements to incrementing the resident “count value” are also provided. Specifically, it is not a requirement of the present invention that such updated “count value(s)” of a replica update transmission must be incremented, and instead any other method or means or arrangement may be substituted to achieve the result of updated “count value(s)” which are greater than the previous local/resident “count value(s)”. Consequently, what is important is that corresponding to a replica update transmission being transmitted, that such replica update transmission comprises an “updated count value” which is greater than the previous known “local/resident count value” of the transmitting machine (such as may be known for example at the time of transmission, or alternatively as may be known at a time when the replica update transmission is prepared for, or begins preparation for, transmission), and also that such previous known “local/resident count value” of the transmitting machine is overwritten/replaced with the transmitted “updated count value”.
The term “distributed runtime system”, “distributed runtime”, or “DRT” and such similar terms used herein are intended to capture or include within their scope any application support system (potentially of hardware, or firmware, or software, or combination and potentially comprising code, or data, or operations or combination) to facilitate, enable, and/or otherwise support the operation of an application program written for a single machine (e.g. written for a single logical shared-memory machine) to instead operate on a multiple computer system with independent local memories and operating in a replicated shared memory arrangement. Such DRT or other “application support software” may take many forms, including being either partially or completely implemented in hardware, firmware, software, or various combinations therein.
The methods of this invention described herein are preferably implemented in such an application support system, such as DRT described in International Patent Application No. PCT/AU2005/000580 published under WO 2005/103926 (and to which U.S. patent application Ser. No. 11/111,946), however this is not a requirement of this invention. Alternatively, an implementation of the methods of this invention may comprise a functional or effective application support system (such as a DRT described in the abovementioned PCT specification) either in isolation, or in combination with other softwares, hardwares, firmwares, or other methods of any of the above incorporated specifications, or combinations therein.
The reader is directed to the abovementioned PCT specification for a full description, explanation and examples of a distributed runtime system (DRT) generally, and more specifically a distributed runtime system for the modification of application program code suitable for operation on a multiple computer system with independent local memories functioning as a replicated shared memory arrangement, and the subsequent operation of such modified application program code on such multiple computer system with independent local memories operating as a replicated shared memory arrangement.
Also, the reader is directed to the abovementioned PCT specification for further explanation, examples, and description of various anticipated methods and means which may be used to modify application program code during loading or at other times.
Also, the reader is directed to the abovementioned PCT specification for further explanation, examples, and description of various anticipated methods and means which may be used to modify application program code suitable for operation on a multiple computer system with independent local memories and operating as a replicated shared memory arrangement.
Finally, the reader is directed to the abovementioned PCT specification for further explanation, examples, and description of various anticipated methods and means which may be used to operate replicated memories of a replicated shared memory arrangement, such as updating of replicated memories when one of such replicated memories is written-to or modified.
In alternative multicomputer arrangements, such as distributed shared memory arrangements and more general distributed computing arrangements, the above described methods of this invention may still be applicable, advantageous, and used. Specifically, any multi-computer arrangement where replica, “replica-like”, duplicate, mirror, cached or copied memory locations exist, such as any multiple computer arrangement where memory locations (singular or plural), objects, classes, libraries, packages etc are resident on a plurality of connected machines and preferably updated to remain consistent, then the methods of this invention are applicable. For example, distributed computing arrangements of a plurality of machines (such as distributed shared memory arrangements) with cached memory locations resident on two or more machines and optionally updated to remain consistent comprise a functional “replicated memory system” with regard to such cached memory locations, and is to be included within the scope of the present invention. Thus, it is to be understood that the aforementioned methods of this invention apply to such alternative multiple computer arrangements. The above disclosed inventive methods may be applied in such “functional replicated memory systems” (such as distributed shared memory systems with caches) mutatis mutandis.
It is also anticipated and envisaged that any of the described functions or operations described as being performed by an optional server machine X (or multiple optional server machines) may instead be performed by any one or more than one of the other participating machines of the plurality (such as machines M1, M2, M3 . . . Mn of FIG. 1).
Alternatively or in combination, it is also further anticipated and envisaged that any of the described functions or operations described as being performed by an optional server machine X (or multiple optional server machines) may instead be partially performed by (for example broken up amongst) any one or more of the other participating machines of the plurality, such that the plurality of machines taken together accomplish the described functions or operations described as being performed by an optional machine X. For example, the described functions or operations described as being performed by an optional server machine X may broken up amongst one or more of the participating machines of the plurality.
Further alternatively or in combination, it is also further anticipated and envisaged that any of the described functions or operations described as being performed by an optional server machine X (or multiple optional server machines) may instead be performed or accomplished by a combination of an optional server machine X (or multiple optional server machines) and any one or more of the other participating machines of the plurality (such as machines M1, M2, M3 . . . Mn), such that the plurality of machines and optional server machines taken together accomplish the described functions or operations described as being performed by an optional single machine X. For example, the described functions or operations described as being performed by an optional server machine X may broken up amongst one or more of an optional server machine X and one or more of the participating machines of the plurality.
Various record storage and transmission arrangements may be used when implementing this invention. One such record or data storage and transmission arrangement is to use “tables”, or other similar data storage structures. Regardless of the specific record or data storage and transmission arrangements used, what is important is that the replicated written-to memory locations are able to be identified, and their updated values (and identity) are to be transmitted to other machines (preferably machines of which a local replica of the written-to memory locations reside) so as to allow the receiving machines to store the received updated memory values to the corresponding local replica memory locations.
Thus, the methods of this invention are not to be restricted to any of the specific described record or data storage or transmission arrangements, but rather any record or data storage or transmission arrangement which is able to accomplish the methods of this invention may be used.
Specifically with reference to the described example of a “table”, the use of a “table” storage or transmission arrangement (and the use of the term “table” generally) is illustrative only and to be understood to include within its scope any comparable or functionally equivalent record or data storage or transmission means or method, such as may be used to implement the methods of this invention.
The terms “object” and “class” used herein are derived from the JAVA environment and are intended to embrace similar terms derived from different environments, such as modules, components, packages, structs, libraries, and the like.
The use of the term “object” and “class” used herein is intended to embrace any association of one or more memory locations. Specifically for example, the term “object” and “class” is intended to include within its scope any association of plural memory locations, such as a related set of memory locations (such as, one or more memory locations comprising an array data structure, one or more memory locations comprising a struct, one or more memory locations comprising a related set of variables, or the like).
Reference to JAVA in the above description and drawings includes, together or independently, the JAVA language, the JAVA platform, the JAVA architecture, and the JAVA virtual machine. Additionally, the present invention is equally applicable mutatis mutandis to other non-JAVA computer languages (including for example, but not limited to any one or more of, programming languages, source-code languages, intermediate-code languages, object-code languages, machine-code languages, assembly-code languages, or any other code languages), machines (including for example, but not limited to any one or more of, virtual machines, abstract machines, real machines, and the like), computer architectures (possible including for example, but not limited to any one or more of, real computer/machine architectures, or virtual computer/machine architectures, or abstract computer/machine architectures, or microarchitectures, or instruction set architectures, or the like), or platforms (possible including for example, but not limited to any one or more of, computer/computing platforms, or operating systems, or programming languages, or runtime libraries, or the like).
Examples of such programming languages include procedural programming languages, or declarative programming languages, or object-oriented programming languages. Further examples of such programming languages include the Microsoft.NET language(s) (such as Visual BASIC, Visual BASIC.NET, Visual C/C++, Visual C/C++.NET, C#, C#.NET, etc), FORTRAN, C/C++, Objective C, COBOL, BASIC, Ruby, Python, etc.
Examples of such machines include the JAVA Virtual Machine, the Microsoft .NET CLR, virtual machine monitors, hypervisors, VMWare, Xen, and the like.
Examples of such computer architectures include, Intel Corporation's x86 computer architecture and instruction set architecture, Intel Corporation's NetBurst microarchitecture, Intel Corporation's Core microarchitecture, Sun Microsystems' SPARC computer architecture and instruction set architecture, Sun Microsystems' UltraSPARC III microarchitecture, IBM Corporation's POWER computer architecture and instruction set architecture, IBM Corporation's POWER4/POWER5/POWER6 microarchitecture, and the like.
Examples of such platforms include, Microsoft's Windows XP operating system and software platform, Microsoft's Windows Vista operating system and software platform, the Linux operating system and software platform, Sun Microsystems' Solaris operating system and software platform, IBM Corporation's AIX operating system and software platform, Sun Microsystems' JAVA platform, Microsoft's .NET platform, and the like.
When implemented in a non-JAVA language or application code environment, the generalized platform, and/or virtual machine and/or machine and/or runtime system is able to operate application code in the language(s) (possibly including for example, but not limited to any one or more of source-code languages, intermediate-code languages, object-code languages, machine-code languages, and any other code languages) of that platform, and/or virtual machine and/or machine and/or runtime system environment, and utilize the platform, and/or virtual machine and/or machine and/or runtime system and/or language architecture irrespective of the machine manufacturer and the internal details of the machine. It will also be appreciated in light of the description provided herein that platform and/or runtime system may include virtual machine and non-virtual machine software and/or firmware architectures, as well as hardware and direct hardware coded applications and implementations.
For a more general set of virtual machine or abstract machine environments, and for current and future computers and/or computing machines and/or information appliances or processing systems, and that may not utilize or require utilization of either classes and/or objects, the structure, method, and computer program and computer program product are still applicable. Examples of computers and/or computing machines that do not utilize either classes and/or objects include for example, the x86 computer architecture manufactured by Intel Corporation and others, the SPARC computer architecture manufactured by Sun Microsystems, Inc and others, the PowerPC computer architecture manufactured by International Business Machines Corporation and others, and the personal computer products made by Apple Computer, Inc., and others. For these types of computers, computing machines, information appliances, and the virtual machine or virtual computing environments implemented thereon that do not utilize the idea of classes or objects, may be generalized for example to include primitive data types (such as integer data types, floating point data types, long data types, double data types, string data types, character data types and Boolean data types), structured data types (such as arrays and records) derived types, or other code or data structures of procedural languages or other languages and environments such as functions, pointers, components, modules, structures, references and unions.
In the JAVA language memory locations include, for example, both fields and elements of array data structures. The above description deals with fields and the changes required for array data structures are essentially the same mutatis mutandis.
Any and all embodiments of the present invention are able to take numerous forms and implementations, including in software implementations, hardware implementations, silicon implementations, firmware implementation, or software/hardware/silicon/firmware combination implementations.
The above arrangements may be implemented by computer program code statements or instructions (possibly including by a plurality of computer program code statements or instructions) that execute within computer logic circuits, processors, ASICs, microprocessors, microcontrollers, or other logic to modify the operation of such logic or circuits to accomplish the recited operation or function. In another arrangement the implementation may be in firmware and in other arrangements may be in hardware. Furthermore, any one or each of these various implementation may be a combination of computer program software, firmware, and/or hardware.
Any and each of the aforedescribed methods, procedures, and/or routines may advantageously be implemented as a computer program and/or computer program product stored on any tangible media or existing in electronic, signal, or digital form. Such computer program or computer program products comprising instructions separately and/or organized as modules, programs, subroutines, or in any other way for execution in processing logic such as in a processor or microprocessor of a computer, computing machine, or information appliance; the computer program or computer program products modifying the operation of the computer on which it executes or on a computer coupled with, connected to, or otherwise in signal communications with the computer on which the computer program or computer program product is present or executing. Such computer program or computer program product modifying the operation and architectural structure of the computer, computing machine, and/or information appliance to alter the technical operation of the computer and realize the technical effects described herein.
For ease of description, some or all of the indicated memory locations herein may be indicated or described to be replicated on each machine, and therefore, replica memory updates to any of the replicated memory locations by one machine, will be transmitted/sent to all other machines. Importantly, the methods and embodiments of this invention are not restricted to wholly replicated memory arrangements, but are applicable to and operable for partially replicated shared memory arrangements mutatis mutandis (e.g. where one or more replicated memory locations are only replicated on a subset of a plurality of machines).
All described embodiments and arrangements of the present invention are equally applicable to replicated shared memory systems, whether partially replicated or not. Specifically, partially replicated shared memory arrangements where some plurality of memory locations are replicated on some subset of the total machines operating in the replicated shared memory arrangement, themselves may constitute a replicated shared memory arrangement for the purposes of this invention.
With reference to FIG. 22, where memory locations “A”, “B”, and “C” are replicated on three machines M1, M2, and M3 of a five machine replicated shared memory arrangement (comprising additional machines M4 and M5), then for the purposes of this invention the term replicated shared memory arrangement is not to be restricted to all 5 machines M1-M5, but may be also encompass any lesser plurality of machines (less than the total number of machines) in the operating arrangement, such as for example machines M1-M3. Thus, machines M1, M2 and M3 with replicated memory locations “A”, “B” and “C” constitute a replicated shared memory arrangement in their own right (without machines M4 or M5).
Typically, the replicated shared memory arrangements described and illustrated within this invention generally are explained to take the form of a plurality of independent machines with independent local memories, such as that depicted in FIGS. 2 and 22. However, various alternative machine arrangements taking the form of a replicated shared memory system are provided by, and included within the scope of, this invention.
Specifically, the term “machine” used herein to refer to a singular computing entity of a plurality of such entities operating as a replicated shared memory arrangement is not to be restricted or limited to mean only a single physical machine or other single computer system. Instead, the use of the term “machine” herein is to be understood to encompass and include within its scope a more broad usage for any “replicated memory instance” (or “replicated memory image”, or “replicated memory unit”) of a replicated shared memory arrangement.
Specifically, replicated shared memory arrangements as described herein take the form of a plurality of machines, each of which operates with an independent local memory. Each such independent local memory of a participating machine within a replicated shared memory arrangement represents an “independent replicated memory instance” (whether partially replicated or fully replicated). That is, the local memory of each machine in a plurality of such machines operating as a replicated shared memory arrangement, represents and operates as an “independent replicated memory instance”. Whilst the most common embodiment of such a “replicated memory instance” is a single such instance of a single physical machine comprising some subset, or total of, the local memory of that single physical machine, “replicated memory instances” are not limited to such single physical machine arrangements only.
For example, the term “machine” includes within its scope any of various “virtual machine” or similar arrangements. One general example of a “virtual machine” arrangement is indicated in FIG. 23. Such virtual machine arrangements may take the form of hypervisor or virtual machine monitor assisted arrangements such as VMWare virtual machine instances, or Xen paravirtualization instances. Alternative substantially equivalent virtual machine arrangements also include Solaris Containers, Isolated Software Domains, Parallel Operating System instances, substantially independent Application Processes or Tasks with independent and/or isolated and/or protected memories, or any other such independent virtual machine instance or such similar multi-program arrangement with an independent or isolated or protected memory. Those skilled in the computing arts will be familiar with various alternative “virtual machine” arrangements.
Utilising any of the various “virtual machine” arrangements, multiple “virtual machines” may reside on, or occupy, a single physical machine, and yet operate in a substantially independent manner with respect to the methods of this invention and the replicated shared memory arrangement as a whole. Essentially then, such “virtual machines” appear, function, and/or operate as independent physical machines, though in actuality share, or reside on, a single common physical machine. Such an arrangement of “n” “virtual machines” N11410 is depicted in FIG. 2.
In FIG. 23, a single physical machine N11401 is indicated comprising hardware N11402 and a hypervisor and/or operating system N11403. Shown to be operating within machine N11401 and above the hypervisor/operating system layer, are n “virtual machines” N11410 (that is, N11410/1, N11410/2 . . . N11410/n), each with a substantially independent, isolated and/or protected local memory (typically taking the form of some subset of the total memory of machine N11401).
Each such “virtual machine” N11410 for the purposes of this invention may taking the form of a single “replicated memory instance”, which is able to behave as, and operate as, a “single machine” of a replicated shared memory arrangement.
When two or more such “virtual machines” reside on, or operate within, a single physical machine, then each such single “virtual machine” will typically represent a single “replicated memory instance” for the purposes of replicated shared memory arrangements. In otherwords, each “virtual machine” with a substantially independent memory of any other “virtual machine”, when operating as a member of a plurality of “replicated memory instance” in a replicated shared memory arrangement, will typically represent and operate as a single “replicated memory instance”, which for the purposes of this invention comprises a single “machine” in the described embodiments, drawings, arrangements, description, and methods contained herein.
Thus, it is provided by this invention that a replicated shared memory arrangement, and the methods of this invention applied and operating within such an arrangement, include a plurality of “replicated memory instances”, which may or may not each correspond to a single independent physical machine. For example, replicated shared memory arrangements are anticipated where such arrangements comprise a plurality (such as for example 10) of virtual machine instances operating as independent “replicated memory instances”, where each virtual machine instance operates within one common, shared, physical machine.
Alternatively for example, replicated shared memory arrangements are anticipated where such arrangements comprise some one or more virtual machine instances of a single physical machine operating as independent “replicated memory instances” of such an arrangement, as well as some one or more single physical machines not operating with two or more “replicated memory instances”.
Further alternatively arrangements of “virtual machines” are also provided and are to be included within the scope of the present invention, including arrangements which reside on, or operate on, multiple physical machines and yet represent a single “replicated memory instance” for the purposes of a replicated shared memory arrangement.
Any combination of any of the above described methods or arrangements are provided and envisaged, and are to be included within the scope of the present invention.
In all described instances of modification, where the application code 50 is modified before, or during loading, or even after loading but before execution of the unmodified application code has commenced, it is to be understood that the modified application code is loaded in place of, and executed in place of, the unmodified application code subsequently to the modifications being performed.
Alternatively, in the instances where modification takes place after loading and after execution of the unmodified application code has commenced, it is to be understood that the unmodified application code may either be replaced with the modified application code in whole, corresponding to the modifications being performed, or alternatively, the unmodified application code may be replaced in part or incrementally as the modifications are performed incrementally on the executing unmodified application code. Regardless of which such modification routes are used, the modifications subsequent to being performed execute in place of the unmodified application code.
It is advantageous to use a global identifier is as a form of ‘meta-name’ or ‘meta-identity’ for all the similar equivalent local objects (or classes, or assets or resources or the like) on each one of the plurality of machines M1, M2 . . . Mn. For example, rather than having to keep track of each unique local name or identity of each similar equivalent local object on each machine of the plurality of similar equivalent objects, one may instead define or use a global name corresponding to the plurality of similar equivalent objects on each machine (eg “globalname7787”), and with the understanding that each machine relates the global name to a specific local name or object (eg “globalname7787” corresponds to object “localobject456” on machine M1, and “globalname7787” corresponds to object “localobject885” on machine M2, and “globalname7787” corresponds to object “localobject111” on machine M3, and so forth).
It will also be apparent to those skilled in the art in light of the detailed description provided herein that in a table or list or other data structure created by each DRT 71 when initially recording or creating the list of all, or some subset of all objects (eg memory locations or fields), for each such recorded object on each machine M1, M2 . . . Mn there is a name or identity which is common or similar on each of the machines M1, M2 . . . Mn. However, in the individual machines the local object corresponding to a given name or identity will or may vary over time since each machine may, and generally will, store memory values or contents at different memory locations according to its own internal processes. Thus the table, or list, or other data structure in each of the DRTs will have, in general, different local memory locations corresponding to a single memory name or identity, but each global “memory name” or identity will have the same “memory value or content” stored in the different local memory locations. So for each global name there will be a family of corresponding independent local memory locations with one family member in each of the computers. Although the local memory name may differ, the asset, object, location etc has essentially the same content or value. So the family is coherent.
It will also be apparent to those skilled in the art in light of the description provided herein that the abovementioned modification of the application program code 50 during loading can be accomplished in many ways or by a variety of means. These ways or means include, but are not limited to at least the following five ways and variations or combinations of these five, including by:

    
    
        (i) re-compilation at loading,
        (ii) a pre-compilation procedure prior to loading,
        (iii) compilation prior to loading,
        (iv) “just-in-time” compilation(s), or
        (v) re-compilation after loading (but, for example, before execution of the relevant or corresponding application code in a distributed environment).
    
    


Traditionally the term “compilation” implies a change in code or language, for example, from source to object code or one language to another. Clearly the use of the term “compilation” (and its grammatical equivalents) in the present specification is not so restricted and can also include or embrace modifications within the same code or language.
Those skilled in the programming arts will be aware that when additional code or instructions is/are inserted into an existing code or instruction set to modify same, the existing code or instruction set may well require further modification (such as for example, by re-numbering of sequential instructions) so that offsets, branching, attributes, mark up and the like are catered for.
Similarly, in the JAVA language memory locations include, for example, both fields and array types. The above description deals with fields and the changes required for array types are essentially the same mutatis mutandis. Also the present invention is equally applicable to similar programming languages (including procedural, declarative and object orientated) to JAVA including Microsoft.NET platform and architecture (Visual Basic, Visual C/C++, and C#) FORTRAN, C/C++, COBOL, BASIC etc.
The terms object and class used herein are derived from the JAVA environment and are intended to embrace similar terms derived from different environments such as dynamically linked libraries (DLL), or object code packages, or function unit or memory locations.
Various means are described relative to embodiments of the invention, including for example but not limited to memory updating means and/or memory replicating means, distributed run time means, modifier or modifying means, and the like. Any one or each of these various means may be implemented by computer program code statements or instructions (possibly including by a plurality of computer program code statements or instructions) that execute within computer logic circuits, processors, ASICs, microprocessors, microcontrollers or other logic to modify the operation of such logic or circuits to accomplish the recited operation or function. In another arrangement, any one or each of these various means may be implemented in firmware and/or in hardware. Furthermore, any one or each of these various means may be implemented by a combination of computer program software, firmware, and/or hardware.
Any and each of the above described methods, procedures, and/or routines may advantageously be implemented as a computer program and/or computer program product stored on any tangible media or existing in electronic, signal, or digital form. Such computer program or computer program products comprising instructions separately and/or organized as modules, programs, subroutines, or in any other way for execution in processing logic such as in a processor or microprocessor of a computer, computing machine, or information appliance; the computer program or computer program products modifying the operation of the computer in which it executes or on a computer coupled with, connected to, or otherwise in signal communications with the computer on which the computer program or computer program product is present or executing. Such a computer program or computer program product modifies the operation and architectural structure of the computer, computing machine, and/or information appliance to alter the technical operation of the computer and realize the technical effects described herein.
The invention may therefore be constituted by a computer program product comprising a set of program instructions stored in a storage medium or existing electronically in any form and operable to permit a plurality of computers to carry out any of the methods, procedures, routines, or the like as described herein including in any of the claims.
Furthermore, the invention includes a plurality of computers interconnected via a communication network or other communications link or path and each operable to substantially simultaneously or concurrently execute the same or a different portion of an application code written to operate on only a single computer on a corresponding different one of computers. The computers are programmed to carry out any of the methods, procedures, or routines described in the specification or set forth in any of the claims, on being loaded with a computer program product or upon subsequent instruction. Similarly, the invention also includes within its scope a single computer arranged to co-operate with like, or substantially similar, computers to form a multiple computer system.
The term “comprising” (and its grammatical variations) as used herein is used in the inclusive sense of “having” or “including” and not in the exclusive sense of “consisting only of”.

## Claims

1. A single computer that utilizes replica memory updating for use in cooperation with at least one other computer in a multiple computer system, wherein said multiple computer system includes a multiplicity of computers, each of the multiplicity of computers being interconnected via at least one communications network, and each executing a different portion of an application program written to execute on a single conventional computer, each having an independent local memory with at least one memory location being replicated in each said local memory; a method of replica memory updating for a single computer in which a memory location of the single computer having a specific location identifier and replicated on at least one other computer of said multiplicity of computers is updated substantially simultaneously from at least one other sources, said single computer comprising:
(i) means for utilizing an updating format for a signal or packet carrying out the replica memory updating, said updating format comprising a specific identifier of the memory location to be updated, a content with which said memory location is to be updated, and a resident updating count of the updating source, said count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating;
(ii) means for storing for each replicated memory location the updating count of the previously sent or received updating;
(iii) means for comparing the presently resident updating count associated with the replicated memory location to be updated with the updating count of the currently received updating signal or packet; said means for comparing further including means overwriting or not overwriting according to the following policies:
(a) if the currently received updating count is greater than the presently resident updating count, overwriting the associated replicated memory location with the currently received data content, and overwriting the presently resident updating count with the currently received updating count; or
(b) if the currently received updating count is less than the presently resident updating count, not overwriting the associated replicated memory location with the currently received data content, and not overwriting the presently resident updating count with the currently received updating count; or
(c) if the currently received updating count is equal to the presently resident updating count, indicating a contention situation.

2. In a single computer used in cooperation with at least one other computer in a multiple computer system, wherein said multiple computer system includes a multiplicity of computers, each of the multiplicity of computers being interconnected via at least one communications network, and each executing a different portion of an application program written to execute on a single conventional computer, each having an independent local memory with at least one memory location being replicated in each said local memory; a method of replica memory updating for a single computer in which a memory location of the single computer having a specific location identifier and replicated on at least one other computer of said multiplicity of computers is updated substantially simultaneously from at least one other sources, said method of replica memory updating in the single computer comprising:
(i) utilizing an updating format for a signal or packet carrying out the replica memory updating, said updating format comprising a specific identifier of the memory location to be updated, a content with which said memory location is to be updated, and a resident updating count of the updating source, said count comprising a number indicative of a sequence of occasions on which the updating source has been updated, inclusive of the current updating;
(ii) storing for each replicated memory location the updating count of the previously sent or received updating;
(iii) comparing the presently resident updating count associated with the replicated memory location to be updated with the updating count of the currently received updating signal or packet; and
(a) if the currently received updating count is greater than the presently resident updating count, overwriting the associated replicated memory location with the currently received data content, and overwriting the presently resident updating count with the currently received updating count; or
(b) if the currently received updating count is less than the presently resident updating count, not overwriting the associated replicated memory location with the currently received data content, and not overwriting the presently resident updating count with the currently received updating count; or
(c) if the currently received updating count is equal to the presently resident updating count, indicating a contention situation.

3. An article of manufacture comprising computer instructions stored in a non-transitory computer readable medium, the computer instructions, when executed by a processor within a computer or information appliance causing modification of the operation of the computer or information appliance in a single computer for use in cooperation with at least one other computer in a multiple computer system, wherein said multiple computer system includes a multiplicity of computers, each of the multiplicity of computers being interconnected via at least one communications network, and each executing a different portion of an application program written to execute on a single conventional computer, each having an independent local memory with at least one memory location being replicated in each said local memory; the modification including performing a method of replica memory updating for a single computer in which a memory location of the single computer having a specific location identifier and replicated on at least one other computer of said multiplicity of computers is updated substantially simultaneously from at least one other sources, said method of replica memory updating in the single computer comprising:
(i) utilizing an updating format for a signal or packet carrying out the replica memory updating, said updating format comprising a specific identifier of the memory location to be updated, a content with which said memory location is to be updated, and a resident updating count of the updating source, said count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating;
(ii) storing, for each replicated memory location, an updating count of a previously sent or received updating;
(iii) comparing the presently resident updating count associated with the replicated memory location to be updated with the updating count of the currently received updating signal or packet; and
(a) if the currently received updating count is greater than the presently resident updating count, overwriting the associated replicated memory location with the currently received data content, and overwriting the presently resident updating count with the currently received updating count; or
(b) if the currently received updating count is less than the presently resident updating count, not overwriting the associated replicated memory location with the currently received data content, and not overwriting the presently resident updating count with the currently received updating count; or
(c) if the currently received updating count is equal to the presently resident updating count, indicating a contention situation.

4. In a single computer used in cooperation with at least one other computer in a multiple computer system, wherein said multiple computer system includes a multiplicity of computers, each interconnected via at least one communications network, and each of the multiplicity of computers executing a different portion of an application program written to execute only on a single conventional computer, each of the multiplicity of computers having an independent local memory with at least one memory location being replicated in each said local memory of each said multiplicity of computers, and a method of detecting contention in replica memory updating in which a memory location having a specific location identifier and replicated on at least one other computer, can be updated substantially simultaneously from at least one source, said method of detecting contention in replica memory updating in the single computer comprising:
(i) utilizing an updating format for the signal or packet carrying out the updating, said format comprising the specific identifier of the memory location to be updated, the content with which said memory location is to be updated, and a resident updating count of the updating source, said count comprising a number indicative of the sequence of occasions on which the updating source has been updated, inclusive of the current updating;
(ii) storing, for each replicated memory location, the updating count of the previously sent or received updating;
(iii) comparing the resident updating count associated with the replicated memory location to be updated with the updating count of the currently received updating signal or packet; and
(iv) indicating a contention situation if the compared updating counts are the same.

5. An article of manufacture comprising computer instructions stored in a non-transitory computer readable medium, the computer instructions, when executed in a processor within a computer or information appliance, causing modification of the operation of a single computer or information appliance operating in multiple computer system that includes a multiplicity of computers, each of the multiplicity of computers interconnected via at least one communications network, and each executing a different portion of an applications program written to execute on a single computer, each having an independent local memory with at least one memory location being replicated in each said local memory, the modification including performing a method of detecting contention in replica memory updating for a single computer in which a memory location having a specific location identifier and replicated on at least one other computer, can be updated substantially simultaneously from at least one source, said method of detecting contention in replica memory updating in a single computer comprising:
(i) utilizing an updating format for the signal or packet carrying out the updating, said format comprising a specific identifier of the memory location to be updated, a content with which said memory location is to be updated, and a resident updating count of the updating source, said count comprising a number indicative of the sequence of occasions on which the updating source has been updated inclusive of the current updating;
(ii) storing, for each replicated memory location, the updating count of the previously sent or received updating;
(iii) comparing the resident updating count associated with the replicated memory location to be updated with the updating count of the currently received updating signal or packet; and
(iv) indicating a contention situation if the compared updating counts are the same.