Method for parallel processing of events within multiple event contexts maintaining ordered mutual exclusion

• US 7,730,501 B2
• Filed: 11/19/2003
• Issued: 06/01/2010
• Est. Priority Date: 11/19/2003
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Chandra, Prashant R., Kumar, Alok
• Primary Examiner(s): Nguyen; Van H
• Application Number:
  US10/718,497
• Publication Number:
  US 20050108718A1
• Time in Patent Office: 2,386 Days
• Field of Search: 719310-314, 719/318, 719330-332, 709/217, 717/135
• US Class Current: 719/331
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

Techniques for parallel processing of events within multiple event contexts include dynamically binding an event context to an execution context in response to receiving an event by storing arriving events into a global event queue and storing events from the global event queue in per-execution context event queues are described. The techniques associate event queues with the execution contexts to temporarily store the events for a duration of the binding and thus dynamically bind the events received on a per-event basis in the context queues.

Claims

1. A method comprising:

at a computer, dynamically binding an event context to an execution context in response to receiving events by;

maintaining the execution context in an idle state until an event arrives at a head of a global event queue that is accessible by event contexts;

storing, in a memory associated with the computer, arriving events into the global event queue;

storing, in the memory, events from the global event queue in per-execution context event queues; and

associating, at the computer, an event queue with the execution context to temporarily store events for the event context for a duration of the dynamic binding;

removing an event from the events for the event context in the event queue;

placing the event in the event queue of other execution context to which the event context associated with the event is already bound to;

determining the event context;

determining if the event context to which the event belongs is already bound to the execution context;

unbinding the event context; and

returning to the idle state.

2. The method of claim 1 wherein the execution context can be in one of four states, idle, binding, bound, or unbinding.

3. The method of claim 1 wherein in the bound state, an execution context is bound to a specific event context and the execution context processes events for that event context and the event queue associated with that execution context is used to store events for the event context to which it is bound.

4. The method of claim 1 wherein in the unbinding state, the execution context determines if it has any more events to process for the event context to which it was bound and either unbinds itself from the event context, going to idle state or begins processing another event from that context, going back to bound state.

5. The method of claim 1 wherein in the event context can be in one of two states, unbound or bound.

6. The method of claim 1 wherein a global FIFO event queue is used to queue events when the events first arrive into a system.

7. The method of claim 1 wherein upon receiving an event, the method further comprises:

assigning an execution context that is in idle state to process the event.

8. The method of claim 1 wherein if the event context is not already bound, binding an execution further comprises:

binding the execution context to that event context by updating a state of the execution context from idle to bound, updating the state of the event context from “

not bound”

to bound, and recording that this execution context is bound to this event context; and

processing the event.

9. The method of claim 8 wherein when the execution context completes processing the event, the execution context transitions to an unbinding state.

10. The method of claim 9 wherein when the execution context completes processing the event, the execution context checks its event queue for additional events to process.

11. The method of claim 9 wherein if there is at least one event in the event queue, the execution context returns to the bound state, removes the event from the event queue and processes the event, otherwise the execution context unbinds itself from the event context, and transitions to an idle state.

12. The method of claim 1 wherein the events are packets.

13. A computer program product residing on a computer readable medium for dynamically binding an event context to an execution context in response to receiving events comprising instructions for causing a processor to:

maintain the execution context in an idle state until an event arrives at a head of a global event queue that is accessible by event contexts;

store events into the global event queue;

store events from the global event queue in per-execution context event queues; and

associate a FIFO event queue with the execution context to temporarily store events for the event context for a duration of the dynamic binding;

remove an event from the events for the event context in the FIFO event queue;

place the event in the FIFO event queue of other execution context to which the event context associated with the event is already bound to;

determine the event context;

determine if the event context to which the event belongs is already bound to the execution context;

unbind the event context; and

return to the idle state.

14. The computer program product of claim 13 wherein upon receiving an event, the method further comprises instructions to:

assign an execution context that is in idle state to process the event.

15. The computer program product of claim 13 wherein if the event context is not already bound, instructions to bind an execution further comprises instructions to:

bind the execution context to that event context by updating a state of the execution context from idle to bound;

update the state of the event context from “

not bound”

to bound;

record that this execution context is bound to this event context; and

process an event.

16. A computer system comprising:

a processor including multiple processing engines, each processing engine including multiple event contexts;

circuitry to dynamically bind an event context to an execution context in response to receiving an event and maintain the execution context in an idle state until an event arrives at a head of a global event queue that is accessible by all event contexts;

the global event queue to store arriving events;

per-execution context event queues to store events from the global event queue; and

a FIFO event queue to temporarily store events for that event context for a duration of the binding, the circuitry further configured to;

remove an event from the events for the event context in the FIFO event queue;

place the event in the FIFO event queue of other execution context to which the event context associated with the event is already bound to;

determine the event context;

determine if the event context to which the event belongs is already bound to the execution context;

unbind the event context; and

return to the idle state.

17. The apparatus of claim 16 wherein the global event queue is used to queue events when the events first arrive into the computer system.