Network traffic event based process priority management

A device may receive a packet associated with an application. The device may identify a filter associated with the application. The device may determine that information associated with the packet matches information associated with the filter. The device may compare a count, associated with the filter, and an expediting threshold associated with expediting processing of the packet based on determining that the information associated with the packet matches the information associated with the filter. The device may selectively expedite processing of the packet based on comparing the count and the expediting threshold.

BACKGROUND

In computing systems, work, such as processes, threads, or the like, may be scheduled by assigning resources to perform the work in accordance with rules, priorities, a scheduling algorithm, or the like. The scheduling of work is typically carried out by a scheduler, which may facilitate one or more objectives, such as maximizing throughput, minimizing response time, minimizing latency, maximizing fairness among processes, or the like.

SUMMARY

According to some possible implementations, a device may include one or more processors to: receive a packet associated with an application; identify a filter associated with the application; determine that information associated with the packet matches information associated with the filter; compare a count, associated with the filter, and an expediting threshold, associated with expediting processing of the packet, based on determining that the information associated with the packet matches the information associated with the filter; and selectively expedite processing of the packet based on comparing the count and the expediting threshold.

According to some possible implementations, a non-transitory computer-readable medium may store instructions that, when executed by one or more processors, cause the one or more processors to: receive a packet associated with an application; determine whether information associated with the packet matches information associated with a filter, where the filter may be associated with the application, where a count may be associated with the filter and may be associated with expediting processing of packets associated with the application; and selectively expedite processing of the packet based on determining whether the information associated with the packet matches the information associated with the filter and based on the count associated with the filter.

According to some possible implementations, a method may include: registering, by a device, a filter associated with expediting processing of packets associated with an application; receiving, by a device, a packet associated with the application; determining, by the device and based on receiving the packet, that information associated with the packet matches information associated with the filter; determining, by the device and based on determining that the information associated with the packet matches the information associated with the filter, whether a count, associated with the filter, satisfies a threshold; and selectively expediting, by the device, processing of the packet based on whether the count satisfies the threshold.

DETAILED DESCRIPTION

A network device (e.g., a router, a switch, a gateway, a firewall, or the like) may host a number of applications associated with providing one or more network services, such as a firewall service, a security service, a packet forwarding service, a packet processing service, or the like. Here, upon receiving a packet associated with an application, the network device may schedule the packet for processing (e.g., by queuing a process, associated with processing the packet, for execution).

In some cases, an application may have a timing requirement, associated with processing packets for the application, that should be satisfied in order to provide the network service. For example, a request, associated with an application (e.g., sent via a particular port, sent by a particular device, or the like) may need to be processed such that a timing requirement, associated with responding to the request, can be satisfied (e.g., in order to avoid a time-out, in order to satisfy a latency requirement, or the like).

Since the network device may host multiple applications, associated with multiple services, the network device may schedule processing of packets, associated with the multiple applications, using a scheduling algorithm. However, the scheduling algorithm may not take into account a need to satisfy such a timing requirement when scheduling a packet for processing by the network device. Thus, satisfaction of the timing requirement may not be guaranteed.

In some cases, the network device may be configured to assign a higher priority level for processing of packets associated with a time-sensitive application (e.g., relative to a priority level for packets associated with an application that is not as time-sensitive). However, the relatively higher priority level may not ensure that the packet is timely processed (e.g., since other packets with the same or even higher priority levels may be similarly scheduled).

Implementations described herein may provide a network device capable of ensuring expedited processing of a packet such that the packet is processed in accordance with a timing requirement. In some implementations, the network device may utilize a filter, associated with the application, to determine that processing of the packet should be expedited. Here, upon receiving a packet that matches the filter, the network device may execute a process (e.g., a process, a thread, or the like), associated with processing the packet, in order to ensure that the packet is processed in accordance with the timing requirement.

In some implementations, the network device may distribute, manage, and monitor a count, associated with the filter, in order to ensure fairness of expedited processing (i.e., in order to ensure that the application does not over-utilize expedited packet processing to the detriment of other applications), as described below. In this way, the network device may ensure that a packet, associated with an application, is processed in accordance with a timing requirement, while also ensuring fairness of expedited processing amongst multiple applications.

FIGS. 1A-1Care diagrams of an overview of an example implementation100described herein. As shown inFIGS. 1A-1C, multiple applications may be hosted by a network device that may be associated with providing one or more network services. As shown, each application may be associated with one or more processes to be executed by the network device in order to provide the one or more network services.

As shown inFIG. 1A, example implementation100may include applications1to N, and may further include a network stack that within which filters, associated with applications1to N, may be registered. A filter may include information, associated with an application, to be used to identify a packet for which the potential for expedited processing is to be determined. For example, the filter may include information that identifies a particular source network address, a particular destination network address, a packet protocol, a particular source port, a particular destination port, a flag associated with a packet header, a particular protocol, a particular pattern of data, or the like.

As further shown, application1may be associated with process A, and application N may be associated with process N. As shown by reference number102, the network stack may register filter F1associated with application1. Similarly, as shown by reference number104, the network stack may register filter FNassociated with application N.

As further shown, the network stack may set an initial count for filters F1and FN. The count may include a value associated with ensuring fairness of expedited processing associated with packets that match the filter and/or are associated with the application. As shown by reference number106, filter F1may have an initial count of 400 that is to incrementally increase from time T0(i.e., time of filter creation) onward. In this case, the count of filter F1incrementally increases by 10 at each scheduling cycle. Thus, the count of filter F1reaches 500 by time T10.

As shown by reference number108, filter FNmay have an initial count of 100 that is to incrementally increase from time T0(i.e., time of filter creation) onward. In this case, the count of filter FNincrementally increases by 20 at each scheduling cycle. Thus, the count of filter FNreaches 300 by time T10. The count may include a value associated with ensuring fairness of expedited processing associated with packets that match the filter and/or are associated with the application. For example, the count may include a numerical value that increases (e.g., by the initial amount upon registration of the filter or incrementally as time passes without receiving a packet that matches the filter) and decreases (e.g., when expedited processing is performed for a packet that matches the filter). In some implementations, the network device may selectively expedite processing of a packet based on the count, as described below.

As shown inFIG. 1B, example implementation100may also include a scheduler. As shown by reference number110, the network stack may receive a first packet, associated with application1, at time T10. As shown by reference number112, the network stack may determine that the first packet matches filter F1(i.e., that the packet is of a type that should be afforded expedited processing).

As shown by reference number114, the network stack may determine that the count, associated with F1, satisfies a threshold of 400 (e.g., 500≥400=YES). Here, the network stack has determined that filter F1has accrued enough count in order to permit expedited processing of the packet. Accordingly, and as shown by reference number116, the network stack may expedite processing of the first packet by, for example, causing the scheduler to schedule process A, associated with application1, for immediate execution. Thereafter, as shown by reference number118, the network stack may decrease the count for filter F1by 300, leaving a remaining count of 200.

As shown inFIG. 1C, and as shown by reference number120, the network stack may receive a second packet, associated with application1, at time T15. As shown by reference number122, the network stack may determine that the second packet also matches filter F1.

As shown by reference number124, the network stack may determine that the count, associated with filter F1, does not satisfy a threshold of 400 (e.g., 250≥400=NO). In this case, because a count amount of 10 has been added at each time unit (e.g., at each scheduling cycle) between T10and T15, the count for filter F1has increased by 50, from 200 to 250, since being decreased. Accordingly, and as shown by reference number126, the network stack may process the second packet normally (e.g., allowing process A to be scheduled according to a scheduling algorithm rather than being scheduled for immediate execution) by, for example, causing the scheduler to schedule process A, associated with application1, for normal execution.

In this way, the network device may ensure that a packet, associated with an application, may be processed in accordance with a timing requirement, while also ensuring fairness of expedited processing amongst multiple applications.

As indicated above,FIGS. 1A-1Care provided merely as an example. Other examples are possible and may differ from what was described with regard toFIGS. 1A-1C.

FIG. 2is a diagram of an example environment200in which systems and/or methods, described herein, may be implemented. As shown inFIG. 2, environment200may include one or more peer devices210, one or more network devices220-1through220-A (A≥1) (hereinafter referred to collectively as “network devices220,” and individually as “network device220”), and a network230. Devices of environment200may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.

Peer device210includes one or more devices capable of receiving and/or providing network traffic. For example, peer device210may include a traffic transfer device, such as a router, a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a server executing a virtual machine, etc.), a security device, an intrusion detection device, a load balancer, or a similar type of device. Additionally, or alternatively, peer device210may include an endpoint device that is a source or a destination for network traffic. For example, peer device210may include a computer or a similar type of device. Peer device210may receive network traffic from and/or may provide network traffic to other peer devices210via network230(e.g., by routing packets using network device(s)220as an intermediary).

Network device220includes one or more devices (e.g., one or more traffic transfer devices) capable of processing, forwarding, and/or transferring traffic between peer devices (e.g., peer devices210) and/or routing devices (e.g., other network devices220). For example, network device220may include a router (e.g., a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router, etc.), a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server), a security device, an intrusion detection device, a load balancer, or any traffic transfer device.

FIG. 3is a diagram of example components of a device300. Device300may correspond to peer device210and/or network device220. In some implementations, peer device210and/or network device220may include one or more devices300and/or one or more components of device300. As shown inFIG. 3, device300may include one or more input components305-1through305-B (B≥1) (hereinafter referred to collectively as input components305, and individually as input component305), a switching component310, one or more output components315-1through315-C (C≥1) (hereinafter referred to collectively as output components315, and individually as output component315), and a controller320.

Input component305may be points of attachment for physical links and may be points of entry for incoming traffic, such as packets. Input component305may process incoming traffic, such as by performing data link layer encapsulation or decapsulation. In some implementations, input component305may send and/or receive packets. In some implementations, input component305may include an input line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more interface cards (IFCs), packet forwarding components, line card controller components, input ports, processors, memories, and/or input queues. In some implementations, device300may include one or more input components305.

Switching component310may interconnect input components305with output components315. In some implementations, switching component310may be implemented via one or more crossbars, via busses, and/or with shared memories. The shared memories may act as temporary buffers to store packets from input components305before the packets are eventually scheduled for delivery to output components315. In some implementations, switching component310may enable input components305, output components315, and/or controller320to communicate.

Output component315may store packets and may schedule packets for transmission on output physical links. Output component315may support data link layer encapsulation or decapsulation, and/or a variety of higher-level protocols. In some implementations, output component315may send packets and/or receive packets. In some implementations, output component315may include an output line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memories, and/or output queues. In some implementations, device300may include one or more output components315. In some implementations, input component305and output component315may be implemented by the same set of components (e.g., and input/output component may be a combination of input component305and output component315).

Controller320includes a processor in the form of, for example, a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and/or another type of processor. A processor is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, controller320may include one or more processors that can be programmed to perform a function.

In some implementations, controller320may include a random access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, an optical memory, etc.) that stores information and/or instructions for use by controller320.

In some implementations, controller320may communicate with other devices, networks, and/or systems connected to device300to exchange information regarding network topology. Controller320may create routing tables based on the network topology information, create forwarding tables based on the routing tables, and forward the forwarding tables to input components305and/or output components315. Input components305and/or output components315may use the forwarding tables to perform route lookups for incoming and/or outgoing packets.

FIG. 4is a diagram of example functional components of network device220. As shown inFIG. 4, network device220may include one or more applications405-1through405-N (N≥1) (hereinafter referred to collectively as applications405and individually as application405), a network stack410, and a scheduler415. In some implementations, applications405, network stack410, and scheduler415are implemented in software that is executed on hardware, such as by a processor, implemented in firmware, or implemented in hardware.

Application405may include an application associated with providing one or more services associated with processing network traffic. For example, application405may provide a firewall service, a security service, a packet forwarding service, a packet monitoring process, a packet inspection service, a packet processing service, or the like. In some implementations, application405may use one or more processes, to be executed using processing resources of network device220, to provide the one or more services.

Network stack410may include a network stack associated with processing packets received by network device220. In some implementations, network stack410may include one or more layers associated with processing packets, such as an Ethernet layer, an Internet protocol (IP) layer, a transmission control protocol and/or user datagram protocol (TCP/UDP) layer, a socket layer, or the like. In some implementations, application405may register a filter, associated with application405, via a socket option of a socket layer of network stack410(e.g., where the socket is associated with application405). In some implementations, network stack410may communicate with scheduler415in order to coordinate processing of packets received by network device220.

Scheduler415may schedule packets for processing by network device220. For example, scheduler415may queue a process, associated with application405, for execution such that a packet, associated with the application, may be processed. In some implementations, scheduler415may manage a packet buffer associated with application405. In some implementations, scheduler415may schedule a packet for processing such that the packet is processed in an expedited manner, as described herein. Additionally, or alternatively, scheduler415may schedule a packet without expedition (e.g., such that the packet is processed normally, using a scheduling algorithm associated with scheduler415). In some implementations, scheduler415may communicate with network stack410in order to coordinate processing of packets received by network device220.

The number and arrangement of functional components shown inFIG. 4are provided as an example. In practice, network device220may include additional functional components, fewer functional components, different functional components, or differently arranged functional components than those shown inFIG. 4. Additionally, or alternatively, a set of functional components (e.g., one or more functional components) of network device220may perform one or more functions described as being performed by another set of functional components of network device220.

FIG. 5is a flow chart of an example process500for determining whether to expedite processing of a packet, associated with an application, based a count of a filter associated with the application.

In some implementations, one or more process blocks ofFIG. 5may be performed by network device220. In some implementations, one or more process blocks ofFIG. 5may be performed by another device or a group of devices separate from or including network device220, such as peer device210.

As shown inFIG. 5, process500may include registering a filter associated with an application (block505). For example, network stack410of network device220may register the filter associated with the application.

The filter may include information, associated with application405, to be used to identify a packet for which the potential for expedited processing is to be determined. For example, the filter may include information that identifies a particular source network address (e.g., an Internet protocol (IP) address), a particular destination network address, a particular source port, a particular destination port, a flag (e.g., a reset flag, a push flag, an urgent flag, or the like) associated with a packet header (e.g., a TCP header), a particular pattern of data, a particular protocol associated with the packet, or the like.

In some implementations, when network device220receives a packet associated with an application, network device220may determine whether the packet matches a filter associated with the application and, if so, may selectively expedite processing of the packet, as described below.

In some implementations, the information associated with the filter may identify a process associated with the filter (e.g., a process associated with the application that is to be executed for processing of the packet). Additionally, or alternatively, the information associated with the filter may identify an initial count amount associated with the filter (e.g., an amount to which the count is to be set upon registration of the filter), an incremental count amount of associated with the filter (e.g., an amount by which the count is periodically increase), a maximum count threshold associated with the filter (e.g., a maximum allowable count associated with the filter), an expediting threshold associated with the filter (e.g., a threshold count amount required to perform expedited packet processing), and/or a decremental count amount of (e.g., an amount by which the count decreases upon performance of expedited packet processing), or the like.

In some implementations, network device220may register the filter based on information associated with application405. For example, application405may provide, to network stack410(e.g., using a socket option associated with a socket layer of network stack410), information associated with the filter, and network stack410may store the information associated with the filter. In some implementations, application405may provide the information associated with the filter based on a configuration of application405(e.g., application405may automatically register the filter). Additionally, or alternatively, application405may provide the information associated with the filter based on user input associated with application405.

In some implementations, network device220may register one or more filters associated with a particular application405. Additionally, or alternatively, network device220may register one or more filters associated with one or more applications.

As further shown inFIG. 5, process500may include increasing a count associated with the filter (block510). For example, network stack410may increase the count associated with the filter.

The count may include a value associated with ensuring fairness of expedited processing associated with packets that match the filter and/or are associated with the application. For example, the count may include a numerical value that increases (e.g., upon registration of the filter or as time passes without receiving a packet that matches the filter) and decreases (e.g., when expedited processing is performed for a packet that matches the filter). In some implementations, network device220may selectively expedite processing of a packet based on the count, as described below.

In some implementations, network stack410may increase the count by setting the count to an initial amount upon registration of the filter. For example, network stack410may set the count to a particular value (e.g., 400 units, 500 units, 100 units, or the like) upon registering the filter. In some implementations, information that identifies the initial count amount may be included in the information associated with the filter. Additionally, or alternatively, network stack410may be configured with a default initial amount to which the count for a newly registered filter is to be set.

Additionally, or alternatively, network stack410may increase the count by an incremental amount. For example, network stack410may increase the count, associated with the filter, by 10 units on a periodic basis (e.g., each time a scheduling cycle starts over, at particular intervals of time, or the like).

In some implementations, network stack410may increase the count by the incremental amount only when expedited processing of a packet, associated with the application, has not occurred for a period of time (e.g., during a most recent scheduling cycle, during a most recent interval of time, or the like). In some implementations, network stack410may increase the count by the incremental amount (e.g., on a periodic basis) while waiting to receive a packet, associated with the application, that matches the filter.

In some implementations, network stack410may incrementally increase the count until a maximum count threshold is reached. For example, network stack410may incrementally increase the count until the count reaches the maximum count threshold (e.g., 5000 units, 1000 units, or the like). Once the count reaches the maximum count threshold, network stack410may not further increase the count until the count is reduced below the maximum count threshold in the manner described below.

In some implementations, information that identifies the incremental count amount may be included in the information associated with the filter. Additionally, or alternatively, network stack410may be configured with a default incremental amount by which to increase the count for the application.

In some implementations, the initial amount and/or the incremental amount may be different for one or more filters of one or more applications405. In this way, network stack410may help ensure packets are processed in accordance with timing requirements while allowing for potentially different priorities and circumstances among processes and/or applications.

In some implementations, the initial amount and/or the incremental amount, associated with application405, may be based on a timing requirement associated with application405. In some implementations, the initial amount and/or the incremental amount may be determined based on an algorithm that receives, as input, information associated with the timing requirement and provides, as output, information that identifies the initial amount and/or the incremental amount.

As further shown inFIG. 5, process500may include receiving a packet associated with the application (block515). For example, network stack410may receive a packet associated with application405.

In some implementations, network stack410may receive the packet (or a notification of the packet), associated with application405, via a port or a socket associated with application405. For example, the packet may be provided by peer device210and/or another network device220.

In some implementations, the packet may undergo processing by one or more layers of network stack410after being received by network stack410. For example, the packet may be processed by an Ethernet layer, an IP layer, a TCP/UDP layer, or the like, of network stack410. Here, when the packet reaches a socket layer of network stack410(e.g., after processing by the other layers), network stack410may proceed with determining whether the packet matches a filter, as described below.

As further shown inFIG. 5, process500may include determining, based on the packet, whether the packet matches a filter associated with the application (block520). For example, network stack410may determine whether the packet matches the filter.

In some implementations, network stack410may determine whether the packet matches the filter based on determining whether the packet includes the information associated with the filter. For example, network stack410may determine whether a source address included in the packet matches a source address identified by the filter, a destination address include in the packet matches a destination address identified by the filter, a source port included in the packet matches a source port identified by the filter, a destination port included in the packet matches a destination port identified by the filter, a particular flag (e.g., associated with a packet header) included in the packet matches a flag identified by the filter, a particular packet protocol associated with the packet, a particular sequence of data in the packet matches a sequence of data identified by the filter, or the like. In some implementations, network stack410may identify one or more filters, associated with the application, and may determine whether the packet matches at least one of the one or more filters.

As further shown inFIG. 5, if the packet does not match the filter (block520—NO), then process500may return to block510to increase the count associated with the filter. For example, in some implementations, if the packet does not match the filter, then network stack410may continue waiting to receive a packet that matches the filter, as described above. Here, network stack410may continue to incrementally increase the count associated with the filter.

As further shown inFIG. 5, if the packet matches the filter (block520—YES), then process500may include determining whether a count, associated with the filter, satisfies a threshold (block525). For example, if the packet matches the filter, then network stack410may determine whether the count, associated with the filter, satisfies an expediting threshold.

In some implementations, the expediting threshold may include information that identifies a count needed for network device220to expedite processing of a packet. For example, the expediting threshold may be a numerical value, such as 500 units, 1000 units, or the like. In some implementations, information that identifies the expediting threshold may be included in the information associated with the filter. Additionally, or alternatively, network stack410may be configured with a default expediting threshold associated with the filter.

In some implementations, network stack410may determine that the count satisfies the expediting threshold when the count is greater than or greater than or equal to the expediting threshold. Additionally, or alternatively, network stack410may determine that the count does not satisfy the expediting threshold when the count is less than or less than or equal to the expediting threshold.

As further shown inFIG. 5, if the count satisfies the threshold (block525—YES), then process500may include expediting processing of the packet (block530). For example, if the count satisfies the expediting threshold, then network stack410may expedite processing of the packet.

Expedited processing of the packet may include causing a process (sometimes referred to as a thread), associated with processing the packet, to be immediately (or substantially immediately) executed by network device220such that the packet may be processed in an expedited manner (e.g., without waiting for the process to be scheduled by scheduler415). In other words, expediting processing of the packet may include causing the process to be queued for immediate execution.

In some implementations, network stack410may expedite processing of the packet based on communicating with scheduler415. For example, network stack410may provide, to scheduler415, an indication that processing of the packet is to be expedited. Here, scheduler415may receive the indication and may identify (e.g., based on information included in the packet, information associated with the filter, etc.) the process associated with processing the packet. Here, scheduler415may immediately (e.g., without queuing, as soon as processing resources are available, etc.) cause the process, associated with the packet, to be executed, and may place the packet in a socket buffer, associated with application405, for processing. The packet may be processed by the process, accordingly.

As further shown inFIG. 5, process500may include decreasing the count, associated with the filter, based on expediting processing of the packet (block535). For example, network stack410may decrease the count, associated with the filter, based on expediting processing of the packet.

In some implementations, network stack410may decrease the count by a decremental amount. For example, network stack410may decrease the count, associated with the filter, by the decremental amount (e.g., 300 units, 100 units, 500 units, or the like) (e.g., each time network stack410causes the process, associated with the processing the packet, to be immediately executed). In some implementations, information that identifies the decremental count amount may be included in the information associated with the filter. Additionally, or alternatively, network stack410may be configured with a default decremental amount by which to decrease the count for the filter. In this way, network stack410may interact with scheduler415in order to facilitate expedited packet processing.

In some implementations, the decremental amount may be different for one or more filters of one or more applications405. In this way, network stack410may help ensure packets are processed in accordance with timing requirements while allowing for potentially different priorities and circumstances among processes and/or applications.

As further shown inFIG. 5, if the count does not satisfy the threshold (block525—NO), then process500may include processing the packet normally (block540). For example, if the count does not satisfy the expediting threshold, then network device220may process the packet normally (e.g., network stack410may not expedite processing of the packet). In some implementations, network stack410may cause the process, associated with processing the packet to be scheduled (e.g., by scheduler415) for execution according to a scheduling algorithm stored or accessible by scheduler415(e.g., placed in a queue corresponding to a priority level of the process). Here, the count will not be decremented by network stack410.

As a specific example of the process described above with reference toFIG. 5, an application SampleApp may include a process (e.g., a process, a thread, or the like) P1, which is associated with port 23. SampleApp may require some packets to be processed immediately (e.g., in order to prevent a time-out). In this case, a TCP header of such packets include a push flag (e.g., a PSH flag). Accordingly, a filter may be registered with the network stack that indicates that a packet, associated with SampleApp in which the PSH flag is set (e.g., “tcp.psh=1”), is to be afforded expedited processing.

Here, the filter may be registered with the network stack via a socket option. In this example, assume that the filter has an initial count of 500, an expediting threshold of 400, and that the count of the filter increases by 10 after each scheduling cycle.

At this point, if a packet, associated with the application, arrives with a PSH flag set, the packet will go through normal TCP processing, and the filter corresponding to the socket will be applied. Here, because the count exceeds the expediting threshold, the packet will be immediately queued into the socket buffer and process P1of SampleApp will be immediately executed (e.g., context switched in).

In such a case, the count for the filter will then be reduced (e.g., by 400). The new count thus becomes 100. Since for each cycle, the count increases by 10, it will take the next 40 iterations of the cycle for process P1to be eligible again for expedited processing. If process P1does not use the count associated with the filter, the count will continue to accumulate until the count reaches a maximum threshold (e.g., 5000). Thereafter, the count will not continue to accrue unless process P1again uses an amount of the count associated with the filter, thus reducing the count below the maximum threshold.

Implementations described herein may provide a network device capable of ensuring expedited processing of a packet such that the packet is processed in accordance with a timing requirement. In some implementations, the network device may utilize a filter, associated with the application, to determine that processing of the packet should be expedited. Here, upon receiving a packet that matches the filter, the network device may execute a process, associated with processing the packet, in order to ensure that the packet is processed in accordance with the timing requirement.

In some implementations, the network device may distribute, manage, and monitor a count, associated with the filter, in order to ensure fairness of expedited processing (i.e., in order to ensure that the application does not over-utilize expedited packet processing to the detriment of other applications), as described below. In this way, the network device may ensure that a packet, associated with an application, is processed in accordance with a timing requirement, while also ensuring fairness of expedited processing amongst multiple applications.