Event management in distributed computing system
US-12155753-B2 · Nov 26, 2024 · US
US9524197B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9524197-B2 |
| Application number | US-201213605548-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 6, 2012 |
| Priority date | Sep 6, 2012 |
| Publication date | Dec 20, 2016 |
| Grant date | Dec 20, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system is provided for multicasting an event notification from an event producer to multiple event listeners, where the event producer and event listeners exist within a computer operating system having a user space, a kernel space, a device space, and an event protocol handler located in the kernel space. The system generates an event indication from an event producer located in the user space, kernel space, or device space, and receiving the event indication in the event protocol handler and generating an event notification. The event producer and the event listeners interface with the event protocol handler to send the event indication and receive the event notification. The event listeners may be located in the user space, kernel space, or device space.
Opening claim text (preview).
The invention claimed is: 1. A method of multicasting an event notification to a plurality of event listeners in a computer system, the method comprising: registering said plurality of event listeners with an events protocol handler through the use of an event management Application Program Interface (API), wherein said event management API is executing within said protocol handler, wherein said events protocol handler located in a kernel space, wherein said event protocol handler interfacing with an extended socket, wherein said extended socket comprising a first portion residing in a user space, wherein said first portion includes event notification application programming interface (API) and a second portion residing in a kernel space, wherein said second portion includes event notification program and wherein said extended socket also comprising a socket buffer; subscribing at least one of said plurality of event listeners for at least one event group via the event management API; creating via an event producer residing in said user space an event indication from an event producer in said events protocol handler using an extended socket API; interfacing said extended socket API with said events protocol handler using said socket buffers, wherein said event notification is mapped from an event queue of said event protocol handler to said socket buffers; and multicasting said event notification to said plurality of event listeners via said events protocol handler and said event management API, wherein said event notification is asynchronous to avoid potential deadlock or blocked processes or threads, wherein when said event notification is sent from the user space using said socket buffers the extended socket API is used and wherein when said event notification is sent from the kernel space or the device space said event notification is handled directly by said events protocol handler. 2. The method of claim 1 wherein said event producer is a programmable device. 3. The method of claim 2 wherein said programmable device runs an operating system, said operating system being different from that used by said user space and said kernel space. 4. The method of claim 1 wherein said programmable device is a field-programmable gate array (FPGA). 5. The method of claim 1 wherein at least one of said plurality of event listeners is a located in said user space and another of said plurality of event listeners is located in a programmable device space. 6. The method of claim 1 wherein at least one of said plurality of event listeners is a located in kernel space and another of said plurality of event listeners is located in a programmable device space. 7. The method of claim 1 , further comprising registering a callback routine via the event management API to be initiated whenever an event notification is generated, the callback routine operable during an interruption of service routine.
via adapters, e.g. between incompatible applications · CPC title
Multiprogramming arrangements · CPC title
Local · CPC title
Event management; Broadcasting; Multicasting; Notifications · CPC title
where tasks reside in different layers, e.g. user- and kernel-space · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.