IP Library › Granted Patent US 10,783,093
Granted Patent B2
US 10,783,093 · App. 16/251,226 · Granted Sep 22, 2020

Driver-to-driver communication

Inventors: Elizabeth J. Dall (Fort Collins, CO); James M. Hull (Saratoga, CA)
Assignee: Hewlett Packard Enterprise Development LP
G06F13/102G06F9/546G06F13/4221H04L49/102
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,783,093
App. No.
16/251,226
Granted
Sep 22, 2020
Kind
B2
Abstract

An example system for driver-to-driver communication can include a first driver located on a first network device and including a transmit data mover (XDM) to send a preformatted message over a fabric interconnect to a second driver located on a second network device. The example system can also include the second driver located on the second network device and including a receive data mover (RDM) to receive the preformatted message, generate an interrupt responsive to receipt of the preformatted message, and route the interrupt to the second driver. The second driver can read the preformatted message responsive to receipt of the interrupt.

Claims (29)

1. A method, comprising:

sending, via a transmit data mover (XDM), a preformatted message over a fabric interconnect from a first driver located on a first network device directly to a receive data mover (RDM) of a second driver located on a second network device;

importing a universal unique identifier (UUID) associated with the first driver; and

tearing down resources associated with the UUID responsive to an unexpected event occurring at the first network device.

2. The method of claim 1 , further comprising transmitting region keys (R-keys) to the RDM for access control.

3. The method of claim 1 , further comprising releasing, to a third driver on a third network device, the resources associated with the UUID responsive to completion of the teardown.

4. The method of claim 1 , further comprising sharing resources between the first driver and the second driver via the fabric interconnect.

5. The method of claim 4 , further comprising ceasing resource sharing responsive to failure of an application using the shared resources on one of the first network device or the second network devices.

6. The method of claim 1 , further comprising sending the preformatted message over a Gen-Z fabric interconnect.

7. A non-transitory machine-readable medium having instructions that when executed by a processor cause the processor to:

communicate a preformatted message directly from a first driver on a first network device to a second driver on a second network device over a fabric interconnect;

identify resources associated with a universally unique identifier (UUID) of the first driver in response to the first preformatted message comprising a free command; and

clean the resources in response to the first preformatted message comprising a tear down command.

8. The medium of claim 7 , wherein the medium comprises a bridge device driver.

9. The medium of claim 7 , further comprising instructions executable to communicate the preformatted message via a first transmit data mover/receive data mover (XDM/RDM) queue pair of the first driver and a second XDM/RDM queue pair of the second driver.

10. The medium of claim 7 , wherein the preformatted message comprises information to clean and teardown the communication.

11. The medium of claim 7 , wherein the first and the second drivers run on different operating systems.

12. The medium of claim 7 , wherein the instructions to communicate the preformatted message directly comprise instructions executable to communicate the preformatted message without intervening factors or intermediaries.

13. A system comprising:

at least one processor;

a non-transitory machine-readable medium having instructions that when executed by the at least one processor cause the at least one processor to:

communicate a preformatted message directly from a first driver on a first network device to a second driver on a second network device over a fabric interconnect;

identify resources associated with a universally unique identifier (UUID) of the first driver in response to the first preformatted message comprising a free command; and

clean the resources in response to the first preformatted message comprising a tear down command.

14. The system of claim 13 , wherein the medium comprises a bridge device driver.

15. The system of claim 13 , where the medium further comprising instructions executable to communicate the preformatted message via a first transmit data mover/receive data mover (XDM/RDM) queue pair of the first driver and a second XDM/RDM queue pair of the second driver.

16. The system of claim 13 , wherein the preformatted message comprises information to clean and teardown the communication.

17. The medium of claim 13 , wherein the first and the second drivers run on different operating systems.

18. The system of claim 13 , wherein the instructions to communicate the preformatted message directly comprise instructions executable to communicate the preformatted message without intervening factors or intermediaries.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 29, 2019
From: DALL, ELIZABETH J.; HULL, JAMES M.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 048168/0736 →
Continuity (1)
Related Publication 20200233817A1 · Jul 23, 2020