Queuing for thread pools using number of bytes

• US 20080301709A1
• Filed: 05/30/2007
• Published: 12/04/2008
• Est. Priority Date: 05/30/2007
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Ban, Bela
• Granted Patent: US 7,992,153 B2
• Time in Patent Office: Days
• US Class Current: 719/314
• CPC Class Codes: H04L 12/1813 for computer conferences, e.g. chat rooms instant messaging H04L51/04; protocols for multimedia communication H04L65/1101; arrangements for multi-party communication H04L65/403; telephonic conference arrangements H04M3/56; television conference systems H04N7/15
• CPC Class Codes: H04L 47/6255 queue load conditions, e.g. longest queue first
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

A method and apparatus for processing message is described. In one embodiment, an application programming interface is configured for receiving and sending messages. A building block layer is coupled to the application programming interface. A channel layer is coupled to the building block layer. A transport protocol stack is coupled to the channel layer for implementing properties specified by the channel layer. The transport protocol stack has a concurrent stack consisting of an out of band thread pool and a regular thread pool. The transport protocol layer is to process messages from each sender in parallel with the corresponding channel for each sender.

Claims

1. A computer-implemented method for processing messages, the method comprising:

receiving messages from a plurality of senders;

queuing the messages from each sender based on a user-defined criteria;

forming a channel for each sender; and

processing the messages from each sender in parallel with the corresponding channel for each sender based on the user-defined criteria.

2. The method of claim 1 wherein the user-defined criteria includes a size of the queue.

3. The method of claim 2 wherein messages from a queue with a larger size are processed before messages from a queue with a smaller size.

4. The method of claim 1 wherein the user-defined criteria includes a number of bytes processed for each sender.

5. The method of claim 4 wherein messages from a queue with a smaller number of bytes are processed before messages from a queue with a larger number of bytes.

6. The method of claim 1 further comprising:

preventing messages from a sender to be processed when the number of bytes of messages already processed for the sender exceeds a cap.

7. The method of claim 1 wherein receiving messages further comprises:

receiving packets from the plurality of senders with a transport protocol stack, the transport protocol stack comprising a multicast receiver thread, a unicast receiver thread, and a connection table.

8. The method of claim 2 further comprising:

sending packets marked as Out of Band to an Out of Band thread pool; and

sending all other packets to a regular thread pool.

9. The method of claim 3 further comprising:

processing a packet with a thread from the regular thread pool.

10. The method of claim 4 further comprising:

forming another thread to process the packet when all threads from the regular thread pool are busy.

11. The method of claim 1 wherein processing messages further comprises:

processing messages for each sender with one thread from a thread pool of a transport protocol stack.

12. The method of claim 6 wherein the thread sends the messages up the transport protocol stack to a corresponding channel of a channel layer, a building block layered on top of the channel layer, and an application programming interface layered on top of the building block.

13. An article of manufacture comprising:

a machine-accessible storage medium including data that, when accessed by a machine, cause the machine to perform a method comprising;

receiving messages from a plurality of senders;

queuing the messages from each sender based on a user-defined criteria;

forming a channel for each sender; and

processing the messages from each sender in parallel with the corresponding channel for each sender based on the user-defined criteria.

14. The article of manufacture of claim 13 wherein the user-defined criteria includes a size of the queue.

15. The article of manufacture of claim 14 wherein messages from a queue with a larger size are processed before messages from a queue with a smaller size.

16. The article of manufacture of claim 13 wherein the user-defined criteria includes a number of bytes processed for each sender.

17. The article of manufacture of claim 16 wherein messages from a queue with a smaller number of bytes are processed before messages from a queue with a larger number of bytes.

18. The article of manufacture of claim 13 wherein processing further comprises:

preventing messages from a sender to be processed when the number of bytes of messages already processed for the sender exceeds a cap.

19. The article of manufacture of claim 13 wherein receiving messages further comprises:

receiving packets from the plurality of senders with a transport protocol stack, the transport protocol stack comprising a multicast receiver thread, a unicast receiver thread, and a connection table.

20. The article of manufacture of claim 13 wherein the method further comprises:

sending packets marked as Out of Band to an Out of Band thread pool; and

sending all other packets to a regular thread pool.

21. The article of manufacture of claim 20 wherein the method further comprises:

processing a packet with a thread from the regular thread pool.

22. The article of manufacture of claim 21 wherein the method further comprises:

forming another thread to process the packet when all threads from the regular thread pool are busy.

23. The article of manufacture of claim 19 wherein processing messages further comprises:

processing messages for each sender with one thread from a thread pool of a transport protocol stack.

24. The article of manufacture of claim 19 wherein the thread sends the messages up the transport protocol stack to a corresponding channel of a channel layer, a building block layered on top of the channel layer, and an application programming interface layered on top of the building block.

25. An apparatus for processing messages comprising:

an application programming interface for receiving and sending messages;

a building block layer coupled to the application programming interface;

a channel layer coupled to the building block layer, the channel layer to form a channel for each sender; and

a transport protocol stack coupled to the channel layer for implementing properties specified by the channel layer, the transport protocol stack comprising a concurrent stack consisting of an out of band thread pool and a regular thread pool, the transport protocol stack configured to receive messages from a plurality of senders, to queue the messages from each sender based on a user-defined criteria, and to process the messages from each sender in parallel with the corresponding channel for each sender based on the user-defined criteria.

26. The apparatus of claim 25 wherein the user-defined criteria includes a size of the queue.

27. The apparatus of claim 26 wherein messages from a queue with a larger size are processed before messages from a queue with a smaller size.

28. The apparatus of claim 25 wherein the user-defined criteria includes a number of bytes processed for each sender.

29. The apparatus of claim 28 wherein messages from a queue with a smaller number of bytes are processed before messages from a queue with a larger number of bytes.

30. The apparatus of claim 25 wherein the transport protocol layer is to further prevent messages from a sender to be processed when the number of bytes of messages already processed for the sender exceeds a cap.

31. The apparatus of claim 25 wherein the transport protocol stack further comprises multicast receiver threads, unicast receiver threads, and a connection table,

wherein the multicast receiver threads, the unicast receiver threads, and the connection table are to receive packets and to forward the packets to the out of band thread pool and the regular thread pool for processing.