Multiple network connections for multiple computers

• US 20080151902A1
• Filed: 10/05/2007
• Published: 06/26/2008
• Est. Priority Date: 10/05/2006
• Status: Abandoned Application

• Current Assignee: John M. Holt
• Original Assignee: John M. Holt
• Inventors: Holt, John M.
• Application Number:
  US11/973,331
• Publication Number:
  US 20080151902A1
• Time in Patent Office: Days
• US Class Current: 370/395.1
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

A system and method for interconnecting multiple computers (M1, M2, . . . , Mn) via at least two independent communications ports (28, 38) are disclosed. Data is sent and received via a data protocol which identifies the sequence position of each data packet in a transmitted sequence of data packets. The packets can be transmitted and/or received out of order. The multiple computers each execute a different portion of an application program written to execute on a single computer.

Claims

1. A multiple computer system comprising a multiplicity of computers each of which is connected to a single communications network via at least two independent communications ports and wherein each of said computers sends and receives data via said network utilising a data protocol in which data packets can be transmitted or received out of sequence.

2. The system as in claim 1, wherein said data protocol identifies the sequence position of each data packet in a transmitted sequence of data packets.

3. The system as in claim 1, wherein later received packets which are later in sequence than earlier received packets overwrite said earlier received packets.

4. The system as in claim 2, wherein later received packets which are later in sequence than earlier received packets overwrite said earlier received packets.

5. The system as in claim 4, wherein later received packets which are earlier in sequence than earlier received packets, do not overwrite said earlier received packets.

6. The system as in claim 5, wherein said later received packets are discarded.

7. The system as in claim 1, wherein each said computer executes a different portion of a single application program written to execute on a single computer.

8. The system as in any one of claim 1, wherein said single communications network is selected from the group of networks consisting of asynchronous transfer mode networks and those networks sold under the trade marks ETHERNET, InfiBand and MYRINET, and any combinations thereof.

9. A single computer for use in the multiple computer system of claim 1.

10. A system comprising a plurality of single computers coupled at least intermittently by a communications network and operating in concert to execute a single application program in parts with replicated memory locations in each of said single computers, each said single computer comprising:

means for executing a different partial portion of an entire application program that is written to execute only one conventional computer;

automated means for modifying said application program to execute in parts on different ones of said single computers;

an independent local memory with at least one memory location being replicated in each said local memory of each of said plurality of single computers;

each of said plurality of computers having at least two independent communications ports and being connected to a single communications network via said at least two independent communications ports;

each of said computers including means for sending and receiving updating data via the at least two independent communications ports utilizing updating data which can be transmitted or received out of sequence.

11. The system as in claim 10, wherein:

said updating data comprising;

(i) an identifier of the replicated memory location to be updated, (ii) a content with which said replicated memory location is to be updated, and (iii) a resident updating count of the updating source associated with the identified replicated memory location