DEVICE, SYSTEM, AND METHOD OF PUBLISHING INFORMATION TO MULTIPLE SUBSCRIBERS

• US 20090024817A1
• Filed: 07/16/2007
• Published: 01/22/2009
• Est. Priority Date: 07/16/2007
• Status: Active Grant

• Current Assignee: Mellanox Technologies TLV Ltd. (NVIDIA Corporation)
• Original Assignee: Voltaire Limited (NVIDIA Corporation)
• Inventors: OVED, Tzah
• Granted Patent: US 7,802,071 B2
• Time in Patent Office: Days
• US Class Current: 711/170
• CPC Class Codes: G06F 13/28 using burst mode transfer, e.g. direct memory access DMA, cycle steal G06F13/32 takes precedence

Abstract

Device, system, and method of publishing information to multiple subscribers. For example, a data publisher capable of communication with one or more subscribers includes: a memory allocator to allocate a memory area of a local memory unit of the data publisher for storing data to be accessible for Remote Direct Memory Access (RDMA) read operations by one or more of said subscribers.

Claims

1. A data publisher capable of communication with one or more subscribers, the data publisher comprising:

a memory allocator to allocate a memory area of a local memory unit of the data publisher for storing data to be accessible for Remote Direct Memory Access (RDMA) read operations by one or more of said subscribers.

2. The data publisher of claim 1, wherein the memory area comprises one or more message stores able to store a plurality of messages corresponding to said data.

3. The data publisher of claim 1, wherein the memory area is registered towards an RDMA-capable hardware component for RDMA read operations.

4. The data publisher of claim 2, wherein a message store of said message stores comprises a cyclic buffer, wherein the data publisher is to locally write messages to said cyclic buffer, and wherein the one or more subscribers are to read messages from said cyclic buffer.

5. The data publisher of claim 2, wherein the one or more subscribers are to remotely pull on demand at least some of said messages from at least one of the message stores.

6. The data publisher of claim 5, wherein a first subscriber is authorized by the data publisher to pull data from a first message store and is not authorized by the data publisher to pull data from a second message store.

7. The data publisher of claim 2, wherein at least one of the subscribers is to perform a Remote Direct Memory Access (RDMA) read operation on said memory area to pull at least some of said messages.

8. The data publisher of claim 2, wherein at least one of the subscribers is to read from said memory area by bypassing an Operating System (OS) of the data publishers.

9. The data publisher of claim 2, wherein a first subscriber is to remotely pull messages from said memory area at a first pace, and a second subscriber is to remotely pull messages from said memory area at a second, different, pace.

10. The data publisher of claim 1, wherein the one or more subscribers are decoupled from the data publisher, and wherein the one or more subscribers are to remotely pull data from said memory area independent of a timing scheme common to the data publisher and the one or more subscribers.

11. The data publisher of claim 7, wherein at least one of the subscribers is to perform the RDMA read operation through InfiniBand hardware.

12. The data publisher of claim 5, wherein at least one of the subscribers is to remotely pull said messages using RDMA read operation through InfiniBand hardware and by bypassing an Operating System (OS) of the data publisher.

13. The data publisher of claim 2, wherein at least one of the subscribers is to remotely read messages from the message stores over RDMA-capable, kernel driver-bypassing and OS-bypassing capable hardware.

14. The data publisher of claim 2, wherein the data publisher comprises:

a publisher application to receive incoming data from an external data provider, to re-format the incoming data into messages, and to write the messages into the one or more message stores.

15. The data publisher of claim 14, wherein the incoming data comprises stock trading information, wherein a message store is to store data related to stock trading information associated with a first set of one or more stocks, and wherein a second message store is to store data related to stock trading information associated with a second, different, set of one or more stocks.

16. The data publisher of claim 2, wherein a common structure of said messages comprises a message header and a message body, and wherein the message header comprises a validity parameter field, a message serial number field, and a field indicating the size of the message body.

17. A method of publishing data to one or more subscribers, the method comprises:

allocating a memory area of a local memory unit of a data publisher for storing data to be accessible for Remote Direct Memory Access (RDMA) read operations by one or more of said subscribers.

18. The method of claim 17, comprising:

creating in the memory area one or more message stores able to store a plurality of messages corresponding to said data.

19. The method of claim 18, wherein creating a message store comprises creating a cyclic buffer to which the data publisher is able to locally write messages and from which the subscribers are able to read messages.

20. The method of claim 18, comprising:

authorizing to one or more subscribers to remotely pull on demand at least some of said messages from at least one of the message stores.

21. The method of claim 20, comprising:

authorizing to a first subscriber to pull data from a first message store; and

un-authorizing to the first subscriber to pull data from a second message store.

22. The method of claim 18, comprising:

authorizing to at least one of the subscribers to perform a Remote Direct Memory Access (RDMA) read operation on said memory area to pull at least some of said messages.

23. The method of claim 18, comprising:

authorizing to at least one of the subscribers to read from said memory area by bypassing an Operating System (OS) of the data publisher.

24. The method of claim 18, comprising:

authorizing to a first subscriber to remotely pull messages from said memory area at a first pace; and

authorizing to a second subscriber to remotely pull messages from said memory area at a second, different, pace.

25. The method of claim 17, comprising:

decoupling the one or more subscribers from the data publisher; and

authorizing the one or more subscribers to remotely pull data from said memory area independent of a timing scheme common to the data publisher and the subscribers.

26. The method of claim 22, comprising:

authorizing to at least one of the subscribers to perform the RDMA read operation through InfiniBand hardware.

27. The method of claim 18, comprising:

authorizing to at least one of the subscribers to remotely read messages from the message stores over RDMA-capable, kernel driver-bypassing and OS-bypassing capable hardware.

28. The method of claim 18, comprising:

receiving incoming data from an external data provider;

re-formatting the incoming data into messages; and

writing the messages into the one or more message stores.

29. The method of claim 28, wherein the incoming data comprises stock trading information, and wherein writing comprises:

writing into a first message store data related to stock trading information associated with a first set of one or more stocks; and

writing into a second message store data related to stock trading information associated with a second, different, set of one or more stocks.

30. The method of claim 18, wherein a common structure of said messages comprises a message header and a message body, and wherein the message header comprises a validity parameter field, a message serial number field, and a field indicating the size of the message body.

31. The method of claim 20, comprising:

authorizing to at least one of the subscribers to remotely pull said messages using RDMA read operation through InfiniBand hardware and by bypassing an Operating System (OS) of the data publisher.