International Business Machines Corporation

Mohan B Sharma

Leo Yue Yeung

Laurie Beth Turner

Gary Randall Horn

Daniel Dean Heimsoth

Willibald A Doeringer

Douglas H Dykeman

Mehdi M Nassehi

Yue T Yeung

Chunhsiang Cheng

Gunter Karjoth

Leo Yue Tak Yeung

A method, system and product for dynamically managing a pool of execution units in a server system, the pool devoted to a communication process between client and server processes. A minimum and a maximum number of execution units in the communication process poolis established. The minimum number of execution units is the number necessary to support a typical client load. The maximum number of execution units is an upper bound to support a peak client load without overloading the server system. As client requests for service are received by the server system, a number of determinations are made. It is determined whether assigning an execution unit to the request would bring a current number of execution units in the communication process pool over the maximum number of execution units. If so, the client request is rejected. It is determined whether assigning an execution unit to the request would bring the number of assigned execution units to a client task making the request over an allotted number of execution units for the client task. If so, the client request is rejected. The client request if the determinations are negative thereby assigning an execution unit in the commnication process pool to the client request. The number of unused execution units in the communication pool is periodically reviewed to determine whether it should be increased or decreased to improve system performace.

Dynamic execution unit management for high performance user level network server system

An object oriented representation for sending network protocol requests between a first and a second process in a computer network. In an object oriented implementation of a protocol stack a network definition object is used for defining an interface to a communication endpoint for a client application and a network address object for defining the communication endpoint. The protocol stack is formed by layers of instances of a protocol interface class object for defining protocol interface for a protocol layer in the protocol stack and a protocol layer class object for defining the protocol layers in the stack. The network protocol requests are sent in an instance of one of a set of network operation classes each of which correspond to a method in the protocol interface class. The client requests are wrapped in the network operation object which contains all the necessary information so the request can be presented to the appropriate protocol layer object in the protocol stack.

Object oriented representation of network requests in a client server

An object oriented network event management framework for managing network protocol events in a computer network. The framework contains a network protocol event class object which includes a first set of network protocol event types, i.e. class definitions, which occur at multiple protocol layers. The network protocol event class object also includes a second set of network protocol event types which occur at specific protocol layers. A network protocol event object is derived from the network protocol event class which specifies network protocol event types from the first and second sets in the network protocol event object which are of interest to an application in the network. Events of the specified network protocol event types are stored in the network protocol event object as the events occur in the network. Upon request, the stored events sent to the application.

Object oriented network event management framework

Variable length data sequence backtracking a trie structure

An object oriented protocol interface for establishing a communication path between communication endpoints in a computer network. The generic nature of the interface allows any and several protocol layers to be developed from the same set of protocol class objects. The interface to a communication endpoint for a client application is defined by instantiating a network definition object for the communication endpoint from a network definition class object. The communication endpoint itself is represented by instantiating a network address object from a network address class object. The protocol layers which form the protocol stack are derived from a set of protocol interface objects from a protocol interface class object and a set of protocol layer objects from a protocol layer class object. The objects forming each of the layers in the protocol stack differ in their capabilities according to their respective layer and the protocol which is provided by the protocol stack. The communication path is established in the protocol stack by calling methods in the sets of protocol interface and protocol layer objects.

Object-oriented communication interface for network protocol access

In a multiprotocol environment, a new socket structure which moves the decision on which protocol to use until the time that the connection is actually made between nodes in the network. The new socket structure is created for every endpoint. All the protocols which could potentially be used to send or receive data is sent a request to create a protocol control block at the time the new socket is created. A selection process determines which of the protocols could be used by the endpoint. The new socket then contains information on each selected protocol. At the time a connection is established, any of the selected protocols could be used. The choice of which protocol to use can be based on user preferences, which protocols are available, the name of the service unit.

Growing community of inventors

Austin, TX, United States of America

Mohan B Sharma