Patent Document

BACKGROUND  
         [0001]    1. Technical Field  
           [0002]    Embodiments of the present invention generally relate to computer processors. More particularly, embodiments relate to packet scheduling in network processors.  
           [0003]    2. Discussion  
           [0004]    In the highly competitive computer industry, the trend toward faster processing speeds and increased functionality is well documented. While this trend is desirable to the consumer, it presents significant challenges to processor designers as well as manufacturers. A particular challenge relates to the processing of packets by network processors. For example, a wide variety of applications such as multi-layer local area network (LAN) switches, multi-protocol telecommunications products, broadband cable products, remote access devices and intelligent peripheral component interconnect (PCI version 2.2, PCI Special Interest Group) adapters use one or more network processors to receive and transmit packets/cells/frames. Network processors typically have one or more microengine processors optimized for high-speed packet processing. Each microengine has multiple hardware threads. A network processor also typically has a general purpose processor on chip. Thus, in a network processor, a receive thread on a microengine will often transfer each packet from a receive buffer of the network processor to one of a plurality of queues contained in an off-chip memory such as a synchronous dynamic random access memory (SDRAM). Queue descriptor data is stored in a somewhat faster off-chip memory such as a static RAM (SRAM).  
           [0005]    Each queue may have an associated type of service (TOS) ranging from network control, which typically has the highest priority to best-effort TOS, which often has the lowest priority. Information stored in the packet headers can identify the appropriate TOS for the packet to obtain what is sometimes referred to as “differentiated service” approach.  
           [0006]    Once the packets are assembled in the DRAM, either the general purpose on chip processor, or one or more micro-engines classify and/or modify the packets for transmission back out of the network processor. A microengine transmit thread determines the queues from which to consume packets based on queue priority and/or a set of scheduling rules. A number of scheduling techniques have evolved in recent years in order to determine when the transmit thread is to transition from one queue to another.  
           [0007]    One queue transition approach follows a strict priority rule, in which the highest priority queue must be empty before packets will be transmitted from the next highest priority queue. This technique is shown in FIG. 10 at method  23  and can result in insufficient consumption from the lower priority queues or “starvation”. Such a result can become particularly acute in processing environments having heavy packet traffic. Another technique is to transition between the queues in a “Round Robin” fashion, in which one packet is transmitted from each queue, regardless of priority. FIG. 11 illustrates a conventional Round Robin approach at method  25 . While the Round Robin technique can be useful in certain circumstances, the inherent disregard for queue priority can lead to significant unfairness in bandwidth allocation. Yet another technique has been to deplete each queue by a weighted amount depending upon the respective type of service and is described in “Efficient Fair Queuing using Deficit Round Robin”, M. Shreedhar et al., ACM SIGCOMM &#39;95. FIG. 9 shows a conventional Deficit Round Robin (DRR) approach at method  21 . While conventional DRR can address some of the shortcomings associated with conventional scheduling techniques, certain implementation difficulties remain.  
           [0008]    The conventional DRR implementation shown in FIG. 9 is a single-threaded implementation that is suitable for a general purpose processor. However, general purpose processors are significantly slower than multi-threaded, multi-processor network processors in processing and scheduling packets. For example, one commercially available network processor uses as many as sixteen receive threads and six transmit threads to populate and read from the plurality of queues. Each queue is therefore shared by multiple threads. A DRR implementation that scales to high-speeds is therefore required for multi-threaded multiprocessor network processor architectures. Such an implementation would require the sharing of queue descriptors between multiple threads. Furthermore, the priority information is stored along with the queue descriptors in an off-chip location. As a result, a considerable amount of processing time can be expended in making the determination of whether to transition to the next queue. There is therefore a need for a system and method of processing packets in a multi-threaded multi-processor architecture that accounts for queue priority without sacrificing speed or performance. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0009]    The various advantages of embodiments of the present invention will become apparent to one skilled in the art by reading the following specification and appended claims, and by referencing the following drawings, in which:  
         [0010]    [0010]FIG. 1 is a block diagram of an example of a networking architecture in accordance with one embodiment of the invention;  
         [0011]    [0011]FIG. 2 is a block diagram of an example of a network processor and off-chip memories in accordance with one embodiment of the invention;  
         [0012]    [0012]FIG. 3 is a block diagram of an example of an on-chip memory in accordance with one embodiment of the invention;  
         [0013]    [0013]FIG. 4 is a data flow diagram of an example of a packet enqueuing and dequeuing process in accordance with one embodiment of the invention.  
         [0014]    [0014]FIG. 5 is a flowchart of an example of a method of processing packets in accordance with one embodiment of the invention;  
         [0015]    [0015]FIG. 6 is a flowchart of an example of a method of processing packets in accordance with one embodiment of the invention;  
         [0016]    [0016]FIG. 7 is a flowchart of an example of a process of updating a queues with credit vector in accordance with one embodiment of the invention;  
         [0017]    [0017]FIG. 8 is a flowchart of an example of a process of receiving packets in accordance with one embodiment of the invention;  
         [0018]    [0018]FIG. 9 is a flowchart of an example of a conventional deficit round robin approach to queue transition;  
         [0019]    [0019]FIG. 10 is a flowchart of an example of a conventional strict priority approach to queue transition; and  
         [0020]    [0020]FIG. 11 is a flowchart of an example of a conventional round robin approach to queue transition. 
     
    
     DETAILED DESCRIPTION  
       [0021]    [0021]FIG. 1 shows a networking blade architecture  20  in which a network processor  22  communicates over a bus  24  with a number of Ethernet media access controllers (MACs)  26 ,  28  in order to classify, modify and otherwise process packets presented at ports  1 -X. The network processor  22  also communicates over static random access memory (SRAM) bus  30  with SRAM  32 , and over synchronous dynamic RAM (SDRAM) bus  34  with SDRAM  36 . Although Ethernet MACs (Institute of Electrical and Electronics Engineers, 802.3) are illustrated, it should be noted that other network processing devices may be used.  
         [0022]    Thus, the architecture  20  can be used in a number of applications such as routers, multi-layer local area network (LAN) switches, multi-protocol telecommunications products, broadband cable products, remote access devices, and intelligent peripheral component interconnect (PCI) adapters, etc. While the examples described herein will be primarily discussed with regard to Internet protocol (IP) packet routing, it should be noted that the embodiments of the invention are not so limited. In fact, the embodiments can be useful in asynchronous transfer mode (ATM) cell architectures, framing architectures, and any other networking application in which performance and Quality of Service (QoS) are issues of concern. Notwithstanding, there are a number of aspects of IP networking for which the embodiments are uniquely suited.  
         [0023]    Turning now to FIG. 2, one approach to the architecture associated with network processor  22  is shown in greater detail. Generally, a first off-chip memory, SDRAM  36 , has a plurality of queues indicated by Q1, Q2-Qn. While any number of queues may be used, the well known differentiated services standard provides for at least six levels of prioritization—one expedited forwarding class, six assured forwarding classes and one best-effort class. A second off-chip memory, SRAM  32 , stores a credit descriptor and a weight descriptor for each queue. The weight descriptors are indicated by w l , w 2 -w n , and define weighted amounts based on the type of service (TOS) associated with the respective queue. The credit descriptors, shown as c 1 , c 2 -c n , indicate whether the queues have been depleted by the weighted amounts. The network processor  22  is operatively coupled to the SDRAM  36  through SDRAM interface  60 , and to the SRAM  32  through SRAM interface  58 , and includes a transmit buffer  38  and a plurality of transmit threads  40 . The transmit threads  40  transfer packets from the queues in the SDRAM  36  to the transmit buffer  38 , and transition between the queues in response to a depletion of the queues by the weighted amounts.  
         [0024]    By way of example, Q1 is the highest priority queue and has a weighted amount w 1  of four maximum sized packets, while Qn has the lowest priority and therefore has a weighted amount w n  of only one maximum sized packet. Thus, the transmit threads  40  will consume from Q1 until the queue has been depleted by four maximum sized packets and then will consume from Q2 for three maximum sized packets, and so on. It will therefore be appreciated that by relying on the weighted amounts, a technique can be achieved that avoids the starvation difficulties associated with conventional strict priority approaches and the inflexibility associated with convention Round Robin approaches.  
         [0025]    The network processor  22  further includes an on-chip memory such as scratchpad  42  and a scheduler thread  44 . The scheduler thread  44  selects transmit threads  40  for packet transmission, and in the illustrated embodiment, a plurality of transmit micro-engines  46  are each provided with one scheduler thread  44  and three transmit threads  40 . As best seen in FIG. 3, the scratchpad  42  has a queues with packets (QWP) vector  48  and a queues with credit (QWC) vector  50 , where each vector  48 ,  50  has a plurality of bits corresponding to the plurality of queues. Thus, if eight queues are used, the vectors  48 ,  50  have eight bits. By maintaining the vectors  48 ,  50  in the on-chip scratchpad  42 , the transmit threads  40  (FIG. 2) are able to determine when to transition from queue-to-queue without having to access off-chip memory SRAM  32  (FIG. 2). While the vectors  48 , 50  are shown as having a plurality of bits corresponding to the plurality of queues, other configurations are possible.  
         [0026]    Returning now to FIG. 2, the network processor  22  also includes a receive buffer  52  and a plurality of receive threads  54 . The receive threads  54  transfer the packets from the receive buffer  52  to the plurality of queues in SDRAM  36 , and update the appropriate QWP vector  48  (FIG. 3) in scratchpad  42 . The receive threads  54  may also be partitioned into a plurality of receive micro-engines  56 . FIG. 4 further demonstrates the process of enqueuing packets from the receive buffer  52  and dequeuing packets to the transmit buffer  38 .  
         [0027]    Turning now to FIG. 5, a method of processing packets is shown generally at  62 . Processing block  66  provides for using the plurality of transmit threads to transmit packets from a plurality of queues of a first off-chip memory to a transmit buffer. As seen in block  68 , the transmit threads transition between the queues in response to a depletion of each queue by a weighted amount. Thus, method  62  enables packets to be dequeued efficiently in a multi-threaded architecture.  
         [0028]    [0028]FIG. 6 demonstrates a scheduling process in greater detail at method  70 . Method  70  can be implemented by the scheduler thread to efficiently schedule packets in an environment in which multiple queues are shared by multiple threads. Specifically, processing block  72  provides for finding the first bit in the QWC vector that is set. It will be appreciated that the end of a round is indicated whenever the QWC vector goes to zero.  
         [0029]    If it is determined at block  74  that no bits in the QWC vector are set, the QWP vector is copied to the QWC vector at block  76 . It is assumed that there will be no packet larger in size than the weight of the queue. Thus, at least one packet is transmitted from each non-empty queue in each round, and each queue with packets will have credit to transmit a packet at the start of a round. If it is determined at block  74  that the QWC vector is not zero, the scheduler thread transitions directly to block  78  and schedules a transmit thread for transmission of the data in the queue corresponding to the first bit set in the QWC. It is important to note that the QWC and QWP vectors are maintained in on-chip scratch pad memory in this embodiment and therefore can be accessed much faster than under conventional approaches.  
         [0030]    Turning now to FIG. 7, the transfer of packets using the transmit threads is shown in greater detail at method  80 . Each of the plurality of transmit threads implement method  80  in the multi-threaded environment. Block  82  provides for transmitting the current packet from the assigned queue, and block  84  provides for determining whether the queue is empty after the transmission. If not, the credit corresponding to the selected queue decremented by the next packet size at next packet size at block  86 . If it is determined at block  88  that the credit for the selected queue is greater than zero, the transmit thread transitions to the end of the procedure. Otherwise, the bit in the QWC vector corresponding to the queue is cleared at block  90 , and the queue weight is added to the queue credit at block  92 . This indicates that no more packets are to be transmitted from the selected queue in the current round. If it is determined at block  84  that the queue is empty, the bits in the QWC and QWP vectors corresponding to the queue are cleared at block  94 .  
         [0031]    Turning now to FIG. 8, one approach to receiving packets is shown in greater detail at method  100 . Specifically, processing block  102  provides for enqueuing an incoming packet to the queue. A determination is made at block  104  as to whether the queue was previously empty. If so, the credit of the queue is initialized at block  106 , and the appropriate bit is set in the QWP vector at block  108 .  
         [0032]    Thus each queue can be given a weight and credit field, with the relative weight being proportional to the relative bandwidth for the queue. The credit field is updated with the weight, and is used to determine which packets to schedule next. When the credit becomes negative, no other packets are transmitted from that queue in that round. In addition to the two fields for each queue, embodiments use QWP and QWC vectors for bookkeeping in determining the next packets to send. The use of these two vectors facilitates the distribution of the scheduling tasks among multiple threads for greater overall efficiency. Furthermore, maintaining the vectors in an on-chip memory location significantly improves speed.  
         [0033]    Those skilled in the art can now appreciate from the foregoing description that the broad techniques of the embodiments of the present invention can be implemented in a variety of forms. Therefore, while the embodiments have been described in connection with particular examples thereof, the true scope of the embodiments of the invention should not be so limited since other modifications will become apparent to the skilled practitioner upon a study of the drawings, specification, and following claims.

Technology Category: 5