SYSTEMS AND METHODS FOR OBJECT RATE LIMITING IN MULTI-CORE SYSTEM

• US 20130246619A1
• Filed: 05/10/2013
• Published: 09/19/2013
• Est. Priority Date: 12/23/2009
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Raja, Murali, Kamath, Sandeep
• Granted Patent: US 9,866,463 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 43/0894 Packet rate
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/12 Protocol engines

Abstract

The present invention is directed towards systems and methods for managing a rate of request for an object transmitted between a server and one or more clients via a multi-core intermediary device. A first core of the intermediary device can receive a request for an object and assume ownership of the object. The first core can store the object in shared memory along with a rate-related counter for the object and generate a hash to the object and counter. Other cores can obtain the hash from the first core and access the object and counter in shared memory. Policy engines and throttlers in operation on each core can control the rate of access to the stored object.

Claims

1. A method for determining if a rate limit for an object has been reached via a multi-core device, the method comprising:

(a) identifying, by a device comprising a plurality of cores and intermediary to a plurality of clients and a server, a rate limit for an application layer object served by the server, the rate limit comprising a predetermined number of requests for the application layer object over a predetermined time period;

(b) tracking, by the plurality of cores, via a counter stored in shared memory accessible by the plurality of cores, a number of requests for the application layer object traversing the device; and

(c) determining, by a first core of the plurality of cores responsive to receiving a request for the application layer object, whether the rate limit for the application layer object has been reached based on the number of requests identified by the counter.

2. The method of claim 1, wherein the rate limit comprises the predetermined number of requests for the application layer object that the device is to process over the predetermined time period.

3. The method of claim 1, wherein step (a) further comprises receiving, by the device, one or more commands specifying a configuration of the rate limit for the application layer object.

4. The method of claim 1, wherein step (b) further comprises designating by the device a second core as an owner of the application layer object.

5. The method of claim 1, wherein step (b) further comprises establishing, by a second core of the plurality of cores, a location in shared memory accessible by the plurality of cores for storing the counter.

6. The method of claim 1, wherein step (c) further comprises determining, by the first core, that the rate limit has been reached.

7. The method of claim 6, further comprising not allowing the client access to the application layer object responsive to the determination.

8. The method of claim 1, wherein step (c) further comprises determining, by the first core, that the rate limit has not been reached.

9. The method of claim 8, further comprising allowing the client access to the application layer object responsive to the determination.

10. The method of claim 1, wherein the application layer object comprises HyperText Transfer Protocol (HTTP).

11. A system for determining if a rate limit for an object has been reached via a multi-core device, the system comprising:

a device comprising a plurality of cores and intermediary to a plurality of clients and a server, wherein the device is configured to identify a rate limit for an application layer object served by the server, the rate limit comprising a predetermined number of requests for the application layer object over a predetermined time period;

wherein the plurality of cores of the device configured to track via a counter stored in shared memory accessible by the plurality of cores, a number of requests for the application layer object traversing the device; and

a first core of the plurality of cores configured to determine responsive to receiving a request for the application layer object, whether the rate limit for the application layer object has been reached based on the number of requests identified by the counter.

12. The system of claim 11, wherein the rate limit comprises the predetermined number of requests for the application layer object that the device is to process over the predetermined time period.

13. The system of claim 11, wherein the device is configured to receive one or more commands specifying a configuration of the rate limit for the application layer object.

14. The system of claim 11, wherein the device is configured to designate a second core as an owner of the application layer object.

15. The system of claim 11, wherein a second core of the plurality of cores is configured to establish a location in shared memory accessible by the plurality of cores for storing the counter.

16. The system of claim 11, wherein the first core is configured to determine that the rate limit has been reached.

17. The system of claim 16, wherein the device is configured to not allow the client access to the application layer object responsive to the determination.

18. The system of claim 11, wherein the first core is configured to determine that the rate limit has not been reached.

19. The system of claim 18, wherein the device is configured to allow the client access to the application layer object responsive to the determination.

20. The system of claim 11, wherein the application layer object comprises HyperText Transfer Protocol (HTTP).