International Business Machines Corporation

Kevin A Bosien

Shawn P Authement

Andrew Dale Walls

Franck Excoffier

Christopher M Dennett

Adam C Chunn

David Mullen

Nhan Q Vo

Razik S Ahmed

Justin C Haggard

Yves A Santos

David S Drinnan

Jake E Miller

A technique for handling storage commands includes receiving, by an interface node of a data storage system, a first storage command. The interface node determines whether the first storage command is a head of queue (HOQ) command. In response to determining the first storage command is an HOQ command, the interface node increments a constrained command count and issues the first storage command to a first worker processor core for processing. In response to determining the first storage command is not an HOQ command, the interface node processes the first storage command as a non-HOQ command.

Techniques for storage command processing

In a data storage system, a hierarchical data structure, such as a file system or a database, is utilized to organize a hierarchical arrangement of device containers corresponding to various device identifiers of the plurality of hardware components in the target hardware system, scripts corresponding to various packet types of communication packets in the target hardware system, and responses corresponding to various packet data in the communication packets in the target hardware system. In response to receipt by a hierarchical emulation engine of a communication packet during emulation of the target hardware system, the communication packet including a device identifier, packet type and packet data, a response to the communication packet is determined by traversing the hierarchical arrangement based on the device identifier, packet type and packet data of the communication packet. The determined response is then provided.

Scriptable hierarchical emulation engine

To emulate a hardware component of a target hardware system including a plurality of hardware components, a component model of the hardware component is built, where the component model includes a register interface through which a host application provides inputs to and reads outputs from the component model, one or more parameter registers that hold values of state variables of the component model, and a state machine that models behavior of the hardware component without explicitly emulating logic implemented in the hardware component. During modeling of the hardware component utilizing the component model the component model is dynamically modified other than by modifying values of the state variables.

Dynamically modifiable component model

Growing community of inventors

Richmond, TX, United States of America

Kevin A Bosien