Methods and systems for hierarchical resource allocation through bookmark allocation

• US 8,306,036 B1
• Filed: 07/16/2008
• Issued: 11/06/2012
• Est. Priority Date: 06/20/2008
• Status: Expired due to Fees

• Current Assignee: F5 Networks, Inc. (F5 Incorporated)
• Original Assignee: F5 Networks, Inc. (F5 Incorporated)
• Inventors: Bollay, Benn
• Primary Examiner(s): CHAN, SAI MING
• Application Number:
  US12/174,262
• Time in Patent Office: 1,574 Days
• Field of Search: 370/468, 370/395.41, 709/226
• US Class Current: 370/395.41
• CPC Class Codes: H04L 47/741 Holding a request until resources become available
• CPC Class Codes: H04L 47/781 Centralised allocation of resources

Abstract

Methods and systems for efficient allocation of resources between child nodes of a parent node in a hierarchical system. The parent node has a limited number of resources available in a resource allocation phrase. The limited number of resources are allocated according to requests from the child nodes in the resource allocation phase. It is determined whether at least one of the child nodes has a request not met by the allocated resources. A bookmark associated with the child node is set for the additional required resources. Additional resources are allocated to the child node according to the bookmark in a subsequent resource allocation phase.

Claims

1. A method for allocating resources between child nodes, the method comprising:

allocating with a traffic management device a limited number of resources of a parent node between child nodes according to requests from the child nodes in a resource allocation phase, wherein the resources comprise tokens representing network bandwidth;

determining with the traffic management device whether at least one of the child nodes has a request not met by the allocated resources;

setting with the traffic management device a bookmark associated with the child node and comprising an indication of the additional required resources; and

allocating with the traffic management device additional resources of the parent node to the child node according to the bookmark in a subsequent resource allocation phase.

2. The method of claim 1, wherein the allocating with the traffic management device additional resources to the child node is determined according to an allocation scheme.

3. The method of claim 2, wherein the allocation scheme is based on at least one of equal distribution between the child nodes, prioritization of the child node, or the relative proportion of requested resources for the child node relative to other child nodes.

4. The method in claim 1, wherein the child nodes are servers using different network communications standards having either reliable or unreliable delivery.

5. The method of claim 4, wherein the different network communications standards are selected from at least one of TCP/IP applications or UDP/IP applications.

6. A non-transitory machine readable medium having stored thereon instructions for allocating resources between child nodes, the stored instructions comprising machine executable code, which when executed by at least one machine processor, causes the processor to perform steps comprising:

allocating a limited number of resources of a parent node between child nodes according to requests from the child nodes in a resource allocation phase, wherein the resources comprise tokens representing network bandwidth;

determining whether at least one of the child nodes has a request not met by the allocated resources;

setting a bookmark associated with the child node and comprising an indication of the additional required resources; and

allocating additional resources of the parent node to the child node according to the bookmark in a subsequent resource allocation phase.

7. The machine readable medium of claim 6, wherein the additional resources are allocated to the child node according to an allocation scheme.

8. The machine readable medium of claim 7, wherein the allocation scheme is based on at least one of equal distribution between the child nodes, prioritization of the child node, or the relative proportion of requested resources for the child node relative to other child nodes.

9. The machine readable medium of claim 6, wherein the child nodes are servers using different network communication standards having either reliable or unreliable delivery.

10. The machine readable medium of claim 9, wherein the different network communications standards are selected from at least one of TCP/IP applications, or UDP/IP applications.

11. A network traffic management apparatus for allocating resources between child nodes, comprising:

a network interface for communication with the child nodes;

a processor coupled to the network interface; and

a memory coupled to the processor, wherein the processor is configured to execute programmed instructions stored in the memory comprising;

allocating a limited number of resources of a parent node between child nodes according to requests from the child nodes in a resource allocation phase, wherein the resources comprise tokens representing network bandwidth;

determining whether at least one of the child nodes has a request not met by the allocated resources;

setting a bookmark associated with the child node and comprising an indication of the additional required resources; and

allocating additional resources of the parent node to the child node according to the bookmark in a subsequent resource allocation phase.

12. The apparatus of claim 11, wherein the additional resources are allocated to the child node according to an allocation scheme.

13. The apparatus of claim 12, wherein the allocation scheme is based on at least one of equal distribution between the child nodes, prioritization of the child node, or the relative proportion of requested resources for the child node relative to other child nodes.

14. The apparatus of claim 11, wherein the child nodes are servers using different network communication standards having either reliable or unreliable delivery.

15. The apparatus of claim 14, wherein the different network communications standards are selected from at least one of TCP/IP applications or UDP/IP applications.