Intel Corporation

Juniper Networks, Inc.

Nazar A Zaidi

Abbas Rashid

Mark Bryers

Ramesh Panwar

Elango Ganesan

David T Hass

Frederick R Gruner

Gary N Hammond

Robert G Hathaway

Fred Gruner

Michael J Morrison

Ricardo Ramirez

Mark Vilas

Michael Freed

Yen C Lee

Sankar Ramanoorthi

John Phillips

Gregory G Spurrier

Yuhong Zhou

Chau Anh Ngoc Nguyen

Bharat N Zaveri

Jeffery J Baxter

Tse-Yu Yeh

Kenneth D Shoemaker

Ken Shoemaker

Umair Azim Khan

Keshavram N Murty

Jeff J Baxter

Mike Morrison

Kin-Yip Liu

Umberto Santoni

Michael Y Chow

Deepak J Aatresh

Jeen Miin

John William Phillips

Anand B Pai

Michael Mroczek

Darshana S Shah

Mike J Morrison

Andrew Paul Kelm

Chau Ahn Ngoc Nguyen

Ramesh Penwar

A network content service apparatus includes a set of compute elements adapted to perform a set of network services; and a switching fabric coupling compute elements in said set of compute elements. The set of network services includes firewall protection, Network Address Translation, Internet Protocol forwarding, bandwidth management, Secure Sockets Layer operations, Web caching, Web switching, and virtual private networking. Code operable on the compute elements enables the network services, and the compute elements are provided on blades which further include at least one input/output port.

Content service aggregation system

A cross-bar switch includes a set of input ports to accept data packets and a set of sink ports in communication with the input ports to forward the data packets. Each sink port includes a communications link interface with a Retry input. When a signal is asserted on the Retry input, the sink port aborts transmission of a data packet and waits a predetermined period of time to retransmit the data packet.

Cross-bar switch incorporating a sink port with retry capability

A cross-bar switch includes a set of input ports for receiving data packets and a set of sink ports for transmitting the received packets to identified targets. A set of data rings couples the input ports to the sink ports. Each sink port utilizes the set of data rings to simultaneously accept multiple data packets targeted to the same destination&#x2014;creating a non-blocking cross-bar switch. Sink ports are also each capable of supporting multiple targets&#x2014;providing the cross-bar switch with implicit multicast capability.

Cross-bar switch having bandwidth allocation

Embodiments include various methods, apparatuses, and systems in which a processor includes an out of order issue engine and an in-order execution pipeline. For some embodiments, the issue engine may be remote from the execution pipeline and execution resources may be many clock cycles away from the issue engine. The issue engine categorizes operations as at least one of either a speculative operations which perform computations, or an architectural operations which has potential to fault or cause an exception. Potentially excepting operations may be decomposed into two separate micro-operations: a speculative micro-operation, which is used to generate data results speculatively so that operations dependent on the results may be speculatively issued, and an architectural micro-operation, which signals the faulting condition for the excepting operation. A STORE operation becomes an architectural operation and all previous faulting conditions may be guaranteed to have evaluated before a STORE is issued.

Decomposing architectural operation into speculative and architectural micro-operations for speculative execution of others and for violation check

An architecture for controlling a multiprocessing system to provide at least one network service to subscriber data packets transmitted in the system using a plurality of compute elements, comprising a management compute element including service set-up information for at least one service and at least one processing compute element applying said at least one network service to said data packets and communicating service set-up information with the management compute element in order to perform service specific operations on data packets. In a further embodiment, a method of controlling a processing system including a plurality of processors is disclosed. The method comprises the steps of operating at least one of said processors as a control authority providing service provisioning information for a subscriber; and operating a set of processors as a service specific compute element responsive to the control authority, receiving provisioning information from the subscriber and performing service specific instructions on data packets to provide IP content services.

Content service aggregation device for a data center

A method comprising fetching an input from at least one of a plurality of floating-point registers and detecting whether the input includes a token. If the token is detected in the input, checking what mode the processor is in. If the processor is in a first mode, processing the input to render an arithmetic result. If the processor is in a second mode, performing a token specific operation. And producing an output. The present invention also provides a processor comprising a first instruction set engine, a second instruction set engine, and a mode identifier. A plurality of floating-point registers are shared by the first instruction set engine and the second instruction set engine. A floating-point unit is coupled to the floating-point registers. The floating-point unit processes an input responsive to the mode identifier and the input to produce an output.

Method and apparatus for achieving architectural correctness in a multi-mode processor providing floating-point support

Embodiments include various methods, apparatuses, and systems in which a processor includes an out of order issue engine and an in-order execution pipeline. For some embodiments, the issue engine may be remote from the execution pipeline and execution resources may be many clock cycles away from the issue engine. The issue engine categorizes operations as at least one of either a speculative operations, which perform computations, or an architectural operation, which has potential to fault or cause an exception. Potentially excepting operations may be decomposed into two separate micro-operations: a speculative micro-operation, which is used to generate data results speculatively so that operations dependent on the results may be speculatively issued, and an architectural micro-operation, which signals the faulting condition for the excepting operation. A STORE operation becomes an architectural operation and all previous faulting conditions may be guaranteed to have evaluated before a STORE is issued.

Resolving all previous potentially excepting architectural operations before issuing store architectural operation

A cross-bar switch includes a set of input ports for receiving data packets and a set of sink ports coupled to the input ports to accept and forward the data packets. Each sink port includes a multiple entry point FIFO with multiple data inputs for receiving data packets. In one implementation, the multiple entry point FIFO includes a FIFO storage buffer and request logic coupling the multiple entry point FIFO's data inputs to the FIFO storage buffer. The multiple entry point FIFO concurrently maintains separate pointers into the FIFO storage buffer for each data packet being received on the multiple entry point FIFO's data inputs.

Cross-bar switch employing a multiple entry point FIFO

Each sink port in a cross-bar switch provides for allocating bandwidth among data packets. Packets are assigned priority levels, and the cross-bar switch regulates bandwidth allocation for each priority level. A sink port records traffic volume for packet data of each priority level. The sink port calculates a weighted average bandwidth for each different priority level and determines whether to reject packet data for the priority level. When the packet data collected by a sink port exceeds a threshold, the sink port rejects data packets with priority levels having excessive weighted average bandwidths.

Cross-bar switch with bandwidth allocation

A cross-bar switch includes a set of input ports for receiving data packets and a set of sink ports for transmitting the received packets to identified targets. A set of data rings couples the input ports to the sink ports. Each sink port utilizes the set of data rings to accept data packets targeted to destinations supported by the sink port. The cross-bar switch includes a multi-sink port for supporting explicit multicast addressing. The multi-sink port is coupled to each data ring and each sink port. The multi-sink port snoops multicast packets on the cross-bar switch's rings and transfers each packet to a set of sink ports that support the packet's targeted destinations.

Cross-bar switch with explicit multicast support

A cross-bar switch includes a set of input ports to receive data packets and a set of sink ports in communication with the input ports to receive the data packets and forward them onto a communications link. Each sink port is adapted to concurrently receive multiple data packets targeted to the same destination or multiple destinations. For example, one sink port receives a first data packet and a second data packet. The one sink port receives at least a portion of the second data packet during a time period in which the one sink port is receiving the first data packet.

Cross-bar switch with sink port accepting multiple packets

Growing community of inventors

San Jose, CA, United States of America

Nazar A Zaidi