Dell Products Inc.

Shrikant U Hallur

Ankit Kumar Singh

Sumanth Vidyadhara

Rohit Kumar Arehalli

Rohitkumar Arehalli

Naveen Awasthy

Methods and systems for managing use and access to memory installed within a data processing system are disclosed. Primary memory (e.g., RAM such as DRAM, SRAM, or the like) that is traditionally non-persistent (e.g., volatile) is configured by a management entity hosted within the data processing system to become persistent (e.g., pseudo-persistent/pseudo non-volatile) to create a persistent reserved primary memory. Data may be stored in the created persistent reserved primary memory to allow processes that previously have to access slower secondary storage to obtain and use the data to be completed faster. The creation of the persistent reserved primary memory may be completed before a full start up process of the data processing system is completed. The data stored in the persistent reserved primary memory may also be retained (e.g., may not be lost) across reboots of the data processing system.

Reserved persistent random access memory

In response to reception of a hypercall addition request, a virtual machine receives a public key. Based on the public key, the virtual machine determines whether the hypercall addition request is valid. In response to the hypercall being valid, the virtual machine adds a hypercall associated with the hypercall addition request within a hypervisor of an information handling system.

Para-virtualized drivers to prevent non-internet protocol hypervisor hypercall denial of service attacks

A flow routing system includes a source device and a destination device that are coupled together via a network that includes a Software Defined Networking (SDN) device. The source device generates a packet that includes a packet header, provides a connection identifier in the packet header, and transmits the packet through the network. The SDN device receives the packet through the network from the source device, matches the connection identifier that is included in the packet header to a single tuple in a flow entry of a flow table and, in response, uses the flow entry to route the packet through the network to the destination device. The connection identifier may be provided by hashing a source IP address, a destination IP address, a VLAN identity, a source MAC address, a source port identifier, a destination port identifier; and a creation time for the flow including the packet.

Flow routing system

Embodiments are directed to transmitting network coding (NC) traffic in heterogeneous networks having both NC and non-NC nodes. A non-NC node, upon receiving the first NC encoded packet will return an error in acknowledgement to the source NC node. The source NC node maintains a table of directly neighbor nodes that indicates whether or not NC is supported. The source NC node decodes the packet for any non-NC destination node and sends the encoded packet to NC nodes per the table. For a non-NC node in the network, the source NC node will send an encoded packet and based on an acknowledgement, the table entry for that node is updated. If NC is supported, the source sends the encoded packet, otherwise it sends the decoded packet.

Growing community of inventors

Bengaluru, India

Shrikant U Hallur