Application-level network queueing

• US 10,547,559 B2
• Filed: 12/26/2015
• Issued: 01/28/2020
• Est. Priority Date: 12/26/2015
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Vasudevan, Anil, Patil, Kiran A., Ilango, Arun Chekhov
• Primary Examiner(s): Ahmed, Atique
• Application Number:
  US14/998,138
• Publication Number:
  US 20170187640A1
• Time in Patent Office: 1,494 Days
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 47/24 Traffic characterised by specific attributes, e.g. priority or QoS
• CPC Class Codes: H04L 47/2475 for supporting traffic characterised by the type of applications
• CPC Class Codes: H04L 47/50 Queue scheduling
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 49/9068 in the network interface card

Abstract

In an example, there is disclosed a computing apparatus, having: a network interface configured to provide a plurality of queues; an application; and one or more logic elements comprising a queuing engine to: inspect an incoming packet; and assign the incoming packet to a dedicated queue for the application based on a classifier. There is also disclosed a method of providing a queuing engine, and one or more tangible, non-transitory computer-readable storage mediums having stored thereon executable instructions for providing a queuing engine.

Claims

1. An apparatus, comprising:

a hardware platform;

a network interface configured to provide a plurality of queues and to operate according to a multi-layer networking protocol stack;

first logic implemented on the hardware platform to provide an application; and

second logic implemented on the hardware platform to provide a queuing engine to;

assign a dedicated queue or group of queues to the application;

receive an incoming packet;

inspect the incoming packet in a top-down fashion to identify a destination port for the incoming packet at an application layer of the multi-layer networking protocol stack;

determine that the destination port deterministically corresponds to the application; and

assign the incoming packet to the dedicated queue or group of queues for the application, comprising using a port number as a key to assign the incoming packet to the dedicated queue or group of queues.

2. The apparatus of claim 1, further comprising means for notifying the application of the assigning.

3. The apparatus of claim 1, further comprising means to enable the application to bypass an interrupt mechanism and to perform per-thread, non-interfering busy polling.

4. The apparatus of claim 1, wherein the queuing engine is further to receive a queue mapping for a socket via an extended socket option.

5. The apparatus of claim 1, wherein the application is to:

receive a notification of the assignment of the dedicated queue or group of queues from the network interface, comprising a queue assignment for a socket, wherein the queue assignment is unique to the application; and

assign the socket to a thread associated with the queue assignment.

6. The apparatus of claim 5, wherein the thread is uniquely associated with the queue assignment in a one-to-one arrangement.

7. The apparatus of claim 5, wherein a plurality of queue assignments is associated with the thread in an n-to-1 arrangement, wherein n>

1.

8. The apparatus of claim 5, wherein the application is to bypass an interrupt mechanism and to perform per-thread, non-interfering busy polling.

9. The apparatus of claim 5, wherein the application is to set queue mapping for the socket via an extended socket option.

10. One or more tangible, non-transitory computer-readable mediums having stored thereon instructions for providing a queuing engine to:

assign a dedicated queue or group of queues to an application;

receive an incoming packet;

inspect the incoming packet on a network interface in a top-down fashion to identify a destination port for the incoming packet at an application layer of a networking protocol stack;

determine that the destination port deterministically corresponds to the application; and

assign the incoming packet to the dedicated queue or group of queues for the application, comprising using a port number as a key to assign the incoming packet to the dedicated queue or group of queues.

11. The one or more tangible, non-transitory computer-readable storage mediums of claim 10, further comprising instructions to notify the application of the assigning.

12. The one or more tangible, non-transitory computer-readable storage mediums of claim 10, further comprising instructions to enable the application to bypass an interrupt mechanism and to perform per-thread, non-interfering busy polling.

13. The one or more tangible, non-transitory computer-readable storage mediums of claim 10, wherein the queuing engine is further to receive a queue mapping for a socket via an extended socket option.

14. One or more tangible, non-transitory computer-readable mediums having stored thereon instructions providing an application to:

receive a notification of an assignment of a dedicated queue or group of queues from a network interface, comprising a queue assignment for a socket, wherein the queue assignment is unique to the application; and

assign the socket to a thread associated with the assignment of the dedicated queue or group of queues based on a port number, wherein the port number functions as an application identifier.

15. The one or more tangible, non-transitory computer-readable storage mediums of claim 14, wherein the thread is uniquely associated with the assignment of the dedicated queue or group of queues in a one-to-one arrangement.

16. The one or more tangible, non-transitory computer-readable storage mediums of claim 14, wherein a plurality of queue assignments is associated with the thread in an n-to-1 arrangement, wherein n>

1.

17. The one or more tangible, non-transitory computer-readable storage mediums of claim 14, wherein the application is to bypass an interrupt mechanism and to perform per-thread, non-interfering busy polling.

18. The one or more tangible, non-transitory computer-readable storage mediums of claim 14, wherein the application is to set queue mapping for the socket via an extended socket option.

19. A method of providing application-level network queuing, comprising:

providing a plurality of queues on a network interface;

providing a network-capable application;

second logic implemented on a hardware platform comprising a queuing engine for;

assigning a dedicated queue or group of queues to the application;

receiving an incoming packet;

inspecting the incoming packet in a top-down fashion to identify a destination port for the incoming packet at an application layer of a networking protocol stack;

determining that the destination port deterministically corresponds to the application; and

assigning the incoming packet to the dedicated queue or group of queues for the application, comprising using a port number as a key to assign the incoming packet to the dedicated queue or group of queues.

20. The method of claim 19, wherein the queuing engine is further to map a queue for a socket via an extended socket option.

21. The method of claim 19, wherein the application is to:

receive a notification of the assignment of the dedicated queue or group of queues having a queue assignment for a socket, wherein the queue assignment is unique to the application; and

assign the socket to a thread associated with the assignment of the dedicated queue or group of queues.

22. The method of claim 21, further comprising uniquely associating the thread with the queue assignment in a one-to-one arrangement.

23. The method of claim 21, wherein a plurality of queue assignments is associated with the thread in an n-to-1 arrangement, wherein n>

1.

24. The method of claim 21, wherein the application is to bypass an interrupt mechanism and to perform per-thread, non-interfering busy polling.

25. The method of claim 21, wherein the application is to set queue mapping for the socket via an extended socket option.