An integrated circuit processes communication packets and comprises a pointer cache and control logic. The pointer cache store pointers that correspond to external buffers that are external to the integrated circuit and configured to store the communication packets. The control logic allocates the external buffers as the corresponding pointers are read from the pointer cache and de-allocates the external buffers as the corresponding pointers are written back to the pointer cache.
|
0. 33. An integrated circuit that processes communication packets, the integrated circuit comprising:
processing facilities configured to create a plurality of external buffers that are external to the integrated circuit and configured to store the communication packets where each external buffer is associated with a pointer that corresponds to the external buffer; and
a pointer cache configured to store the pointers that correspond to the external buffers,
wherein the processing facilities are further configured to:
allocate the external buffers as the corresponding pointers are read from the pointer cache and de-allocate the external buffers as the corresponding pointers are written back to the pointer cache,
transfer an exhaustion signal if a number of the pointers to the de-allocated buffers reaches a minimum threshold, and
create additional external buffers and their corresponding pointers in response to the exhaustion signal.
1. An integrated circuit that processes communication packets, the integrated circuit comprising:
a core processor configured to create a plurality of external buffers that are external to the integrated circuit and configured to store the communication packets where each external buffers is associated with a pointer that corresponds to the external buffer;
a pointer cache configured to store the pointers that correspond to the external buffers;
control logic configured to allocate the external buffers as the corresponding pointers are read from the pointer cache and de-allocate the external buffers as the corresponding pointers are written back to the pointer cache wherein the control logic is configured to transfer an exhaustion signal if a number of the pointers to the de-allocated buffers reaches a minimum threshold; and
the core processor configured to create additional external buffers and their corresponding pointers in response to the exhaustion signal.
17. A method of operating an integrated circuit that processes communication packets, the method comprising:
creating a plurality of external buffers that are external to the integrated circuit and that are configured to store the communication packets, ;
creating a plurality of pointers where each pointer corresponds to one of the plurality of external buffers;
storing a subset of the plurality of pointers in a pointer cache in the integrated circuit;
allocating the external buffers as the corresponding pointers are read from the pointer cache;
de-allocating the external buffers as the corresponding pointers are written back to the pointer cache;
transferring an exhaustion signal if a number of the pointers to the de-allocated buffers reaches a minimum threshold; and
in response to the exhaustion signal, creating additional external buffers and their corresponding pointers where the additional external buffers are external to the integrated circuit and are configured to store the communication packets.
0. 34. An integrated circuit that processes communication packets, the integrated circuit comprising:
processing facilities configured to create a plurality of external buffers that are external to the integrated circuit and configured to store the communication packets where each external buffer is associated with a pointer that corresponds to the external buffer; and
a pointer cache configured to store the pointers that correspond to the external buffers,
wherein the processing facilities are further configured to:
allocate the external buffers by modifying the pointer cache to indicate that pointers in the pointer cache corresponding to the external buffers are in use and de-allocate the external buffers by modifying the pointer cache to indicate that pointers in the pointer cache corresponding to the external buffers are unused,
transfer an exhaustion signal if a number of the pointers in the pointer cache corresponding to the external buffers indicated to be unused reaches a minimum threshold, and
create additional external buffers and their corresponding pointers in response to the exhaustion signal.
0. 51. A method of operating an integrated circuit that processes communication packets, the method comprising:
creating a plurality of external buffers that are external to the integrated circuit and that are configured to store the communication packets;
creating a plurality of pointers where each pointer corresponds to one of the plurality of external buffers;
storing a subset of the plurality of pointers in a pointer cache in the integrated circuit;
allocating the external buffers by modifying the pointer cache to indicate that pointers in the pointer cache corresponding to the external buffers are in use;
de-allocating the external buffers by modifying the pointer cache to indicate that pointers in the pointer cache corresponding to the external buffers are unused;
transferring an exhaustion signal if a number of the pointers indicated to be unused reaches a minimum threshold; and
in response to the exhaustion signal, creating additional external buffers and their corresponding pointers where the additional external buffers are external to the integrated circuit and are configured to store the communication packets.
2. The integrated circuit of
3. The integrated circuit of
4. The integrated circuit of
5. The integrated circuit of
6. The integrated circuit of
7. The integrated circuit of
8. The integrated circuit of
9. The integrated circuit of
10. The integrated circuit of
11. The integrated circuit of
12. The integrated circuit of
13. The integrated circuit of
14. The integrated circuit of
15. The integrated circuit of
16. The integrated circuit of
18. The method of
19. The method of
20. The method of
22. The method of
23. The method of
24. The method of
25. The method of
26. The method of
27. The method of
28. The method of
29. The method of
30. The method of
31. The method of
0. 32. The integrated circuit of
0. 35. The integrated circuit of
0. 36. The integrated circuit of
0. 37. The integrated circuit of
0. 38. The integrated circuit of
0. 39. The integrated circuit of
0. 40. The integrated circuit of
0. 41. The integrated circuit of
0. 42. The integrated circuit of
0. 43. The integrated circuit of
0. 44. The integrated circuit of
0. 45. The integrated circuit of
0. 46. The integrated circuit of
0. 47. The integrated circuit of
0. 48. The integrated circuit of
0. 49. The integrated circuit of
0. 50. The integrated circuit of
0. 52. The method of
0. 53. The method of
0. 54. The method of
0. 55. The method of
0. 56. The method of
0. 57. The method of
0. 58. The method of
0. 59. The method of
0. 60. The method of
0. 61. The method of
0. 62. The method of
0. 63. The method of
0. 64. The method of
0. 65. The method of
0. 66. The method of
|
Buffer classes are used to differentiate services among traffic streams by assigning different streams to different classes of external buffers. Traffic streams offering a higher quality-of-service are typically provided with greater access to external buffers. Bursty traffic may need an elastic exclusive/shared class arrangement. A class may be associated with only one type of traffic, such as Constant Bit Rate (CBR), Available Bit Rate (ABR), Variable Bit Rate (VBR), or Unspecified Bit Rate (UBR). CBR traffic without bursts typically uses static classes. ABR traffic uses exclusive and shared external buffer classes to respectively handle minimum cell rates and bursts. VBR and UBR traffic typically use shared buffer classes.
The external buffers are separated into two separately managed pools A and B. Pools can be used for service differentiation. Pools are also helpful when the external buffers are located in separate memory devices, so each device may have its own independently managed pool.
For each class, control logic 524 tracks the number of pointers in pointer cache 523 that point to the de-allocated external buffers and the number of pointers in pointer cache 523 that point to the allocated external buffers. If the number of pointers to the de-allocated external buffers in one of the classes reaches a minimum threshold for that class, control logic 524 transfers an exhaustion signal for that class to core processor 104. If the class is exclusive, control logic 524 may also borrow pointers from the corresponding fail-over class for use by the exclusive class, although conditions and thresholds may be used to limit the amount of borrowing. Control logic 524 tracks the number of pointers distributed to each class and may re-distribute pointers from one class to another based on certain conditions, such as traffic loads. In addition, more ABR traffic may require more exclusive buffers at the expense of shared buffers where more UBR traffic has the opposite effect.
Scheduler Circuitry—
Scheduler 105 comprises control logic 730, scheduling boards 731-732, and context RAM 735. Board 731 is vertically separated into time periods 741-745 where a “1” indicates a reservation at that time period and a “0” indicates no reservation at that time period. Board 731 is horizontally separated into priority levels 751-754 that are ranked from high at priority level #1 to low at priority level #4. Board 732 is similar to board 731, but has two priority levels and ten time periods. Control logic 730 process boards 731-732 independently of one another.
Context RAM 735 has entries 736 that each hold one of thousands of possible channel descriptor identifiers. The channel descriptors that correspond to these identifiers describe how packet transmission should be handled for a channel. For example, a channel descriptor indicates where packets for the channel are stored and how frequently they should be transmitted. Boards 731-732 are each associated with a different portion of context RAM 735. As indicated by the arrows, each time period at each priority level on each board is associated with its own one of the context RAM entries 736, and thus, with a possibly unique channel descriptor. To serve a reservation, control logic 730 sends a request that identifies the corresponding channel descriptor to co-processor circuitry 107.
In some examples of the invention, there are 64,000 channel descriptors, and thus, 64,000 corresponding board time periods. The 64,000 time periods can be distributed among boards in various combinations of 2,000, 4,000, 8,000, 16,000, 32,000, or 64,000 time periods per board. Boards can be separated into 1, 2, or, 4 priority levels that run concurrently in time. Each priority level uses up time periods, so an 8,000 time period board with four priority levels has 2,000 time periods per priority level that run concurrently. The minimum number of reservations in a given priority level is 512.
At a GET, control logic 730 serves the highest priority reservation at fence 860. Control logic 860 then advances fence 860 to the next time period in the priority level that is served. Control logic 860 also advances fence 860 to the next time period in other priority levels that did not have a reservation at fence 860. Control logic 860 does not advance fence 860 at priority levels that had an un-served reservation at fence 860.
On
The various scheduling boards and priority levels provide a robust mechanism for differentiating services between traffic streams based on service level agreements. For example, the highest priority level of board 732 could be traffic with a guaranteed bandwidth rate, and the lower priority level could be traffic without any bandwidth guarantee. Board 731 has four priority levels and may have Constant Bit Rate (CBR) traffic at the highest priority, real time Variable Bit Rate (VBR) traffic at the second-highest priority, non-real-time VBR traffic at the third-highest priority level, and Available Bit Rate (ABR) traffic at the fourth and lowest priority level. Traffic can also be allocated among boards to provide expensive high-quality service from one board, and cheap moderate-quality service from another board. Prioritization circuitry within co-processor circuitry 107 can assign channels on the high-quality board to the highest priority queue to core processor 104 and assign channels on the moderate-quality board to the highest priority queue to core processor 104.
A board stall occurs when a higher priority level starves a lower priority level, and a reservation at the lower priority level will never get served. In a board stall, control logic 730 does not advance fence 860 until the stall is cured. If a force option is selected, the indicated priority level is serviced at the next GET. If a scan option is selected, the above-described board processing is modified. All reservations in the highest priority level are serviced before any lower priority levels are serviced. In lower priority levels during this time, fence 860 is advanced at a GET if the time period is not reserved. The scan process repeats for the next highest priority level down through the lowest priority level.
Control logic 730 schedules a reservation in response to a “PUT” generated by core processor 104 or scheduler 105. Control logic 730 schedules the reservation by determining a start position. The start position is a number of time periods from the current fence location where the search starts for an available time period for the reservation. The start position may be specified in the PUT, or it may be calculated by control logic 730.
To calculate the start position, control logic 730 first retrieves scheduling parameters from the proper context buffer in co-processor circuitry 107 using a pointer in the PUT. Control logic 730 also increments the in-use count for the context buffer. Control logic 730 then executes dual Guaranteed Cell Rate (GCR) scheduling algorithms based on the scheduling parameters to determine the start position.
The scheduling parameters include a scheduling board indicator, first choice priority level, and second choice priority level that is a higher priority than the first choice. If the first priority level does not work for some reason, then the second priority level is attempted in a priority promotion. In a priority promotion, the control logic 730 tries to find a reservation based on the Minimum Cell Rate (MCR), and if nothing is available, then control logic 730 tries to find a reservation based on the Peak Cell Rate (PCR).
The scheduling parameters also include usage values that determine how the dual algorithms are used. Based on the usage values, algorithm 1 and algorithm 2 are respectively be used for:
The two scheduling algorithms are specified by the following psuedocode where PTt is the present time, TAT1t-1, TAT2t-1 are old times read from the context buffer, and TAT1t, TAT2t are new times written to the context buffer.
if (PUT w/ no update instruction) {
ICI1 = 0
ICI2 = 0
PIPELAT = 0
} // else PUT with update; use the ICIs as provided
TAT2t = max (TAT2t−1 + ICI2, PTt + ICI2)
if (ALG==MCR/PCR)
TAT1start = max (PTt − L1, min (TAT1t−1 + ICI1, PTt + L1))
else TAT1start = max (TAT1t−1 + ICI1, PTt + ICI1)
if (ALG==PCR/none) {
start position = max (0, TAT1t − L1 − PTt)
} else if (ALG==SCR/PCR) {
start position = max (0, TAT2t − L2 − PTt, TAT1t − L1 − PTt)
} else if (ALG==MCR/PCR) {
start position = max (0, TAT2t − L2 − PTt)
}
TAT2t = max (TAT2start, landing position + PTt)
if (ALG==MCR/PCR) TAT1t = TAT1start
else TAT1t = max (TAT1start, landing position + PTt)
if (PUT with write instruction) {
write TAT1t, TAT2t, back to context buffer
}
decrement in-use count.
In addition to determining the starting position, control logic 730 determines the board configuration, fence location, and the oldest reservation at the fence in each priority level. Control logic 730 locates the start position from the fence at the selected priority level and on the selected scheduling board. Control logic 730 then searches for an available reservation time period. If the time period at the start time is already reserved, then the next available time period is reserved.
The number of time periods between the fence and the reserved time period is referred to as the landing position. The landing position must be smaller than the board to avoid wrapping around the board and reserving a time period that is improperly close to the fence. It may be the case that the priority level is full and reservations only open up as the fence is advanced. In this situation, any PUT will be reserved just behind the advancing fence.
Once the reservation is made, the applicable channel descriptor identifier is placed in the corresponding entry in context RAM 735. The scheduling parameters may also be updated and written back to the context buffer. The in-use count for the context buffer is decremented.
Those skilled in the art will appreciate variations of the above-described embodiments that fall within the scope of the invention. As a result, the invention is not limited to the specific examples and illustrations discussed above, but only by the following claims and their equivalents.
Snyder, II, Wilson P., Tompkins, Joseph B., Lussier, Daniel J.
Patent | Priority | Assignee | Title |
9035946, | Feb 13 2014 | ZIMMERMAN, ALVIN D | Computer hardware architecture and data structures for triangle binning to support incoherent ray traversal |
9058691, | Feb 13 2014 | ZIMMERMAN, ALVIN D | Computer hardware architecture and data structures for a ray traversal unit to support incoherent ray traversal |
9087394, | Feb 13 2014 | ZIMMERMAN, ALVIN D | Computer hardware architecture and data structures for packet binning to support incoherent ray traversal |
9619923, | Feb 13 2014 | ZIMMERMAN, ALVIN D | Computer hardware architecture and data structures for encoders to support incoherent ray traversal |
9761040, | Feb 13 2014 | ZIMMERMAN, ALVIN D | Computer hardware architecture and data structures for ray binning to support incoherent ray traversal |
Patent | Priority | Assignee | Title |
5151895, | Jun 29 1990 | ENTERASYS NETWORKS, INC | Terminal server architecture |
5493652, | Apr 29 1994 | IBM Corporation | Management system for a buffer memory having buffers of uniform size in which the buffers are divided into a portion of contiguous unused buffers and a portion of contiguous buffers in which at least some are used |
5606559, | Aug 11 1995 | International Business Machines Corporation; IBM Corporation | System and method for an efficient ATM adapter/device driver interface |
5689707, | Dec 04 1995 | NCR Corporation | Method and apparatus for detecting memory leaks using expiration events and dependent pointers to indicate when a memory allocation should be de-allocated |
5748630, | May 09 1996 | Mindspeed Technologies, LLC | Asynchronous transfer mode cell processing system with load multiple instruction and memory write-back |
5818830, | Dec 29 1995 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | Method and apparatus for increasing the effective bandwidth of a digital wireless network |
5822618, | Nov 21 1994 | Cirrus Logic, Inc. | System for automatically switching to DMA data transfer mode to load and unload data frames when there are excessive data frames in memory buffer |
5920561, | Mar 07 1996 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | ATM communication system interconnect/termination unit |
5978898, | Oct 30 1998 | Intel Corporation | Allocating registers in a superscalar machine |
6046983, | Aug 02 1995 | Nippon Telegraph and Telephone Corporation | Dynamic rate control system |
6061351, | Feb 14 1997 | Advanced Micro Devices, INC | Multicopy queue structure with searchable cache area |
6088777, | Nov 12 1997 | TELEFONAKTIEBOLAGET LM ERICSSON PUBL | Memory system and method for dynamically allocating a memory divided into plural classes with different block sizes to store variable length messages |
6175902, | Feb 14 1997 | AMD TECHNOLOGIES HOLDINGS, INC ; GLOBALFOUNDRIES Inc | Method and apparatus for maintaining a time order by physical ordering in a memory |
6246682, | Mar 05 1999 | F POSZAT HU, L L C | Method and apparatus for managing multiple ATM cell queues |
6324623, | May 30 1997 | Oracle International Corporation | Computing system for implementing a shared cache |
6341325, | Jan 12 1999 | International Business Machines Corporation | Method and apparatus for addressing main memory contents including a directory structure in a computer system |
6401147, | May 24 1999 | GLOBALFOUNDRIES Inc | Split-queue architecture with a first queue area and a second queue area and queue overflow area having a trickle mode and an overflow mode based on prescribed threshold values |
6457112, | Jul 30 1999 | SCSK CORPORATION | Memory block allocation system and method |
6487212, | Feb 14 1997 | GLOBALFOUNDRIES Inc | Queuing structure and method for prioritization of frames in a network switch |
6504846, | May 21 1999 | GLOBALFOUNDRIES Inc | Method and apparatus for reclaiming buffers using a single buffer bit |
6523060, | Apr 07 1995 | Cisco Technology, Inc | Method and apparatus for the management of queue pointers by multiple processors in a digital communications network |
6526499, | Apr 02 1998 | Intel Corporation | Method and apparatus for load buffers |
6539024, | Mar 26 1999 | WSOU Investments, LLC | Method and apparatus for data buffer management in a communications switch |
6601089, | Jun 21 1999 | Oracle America, Inc | System and method for allocating buffers for message passing in a shared-memory computer system |
6621792, | Feb 23 1999 | AVAYA Inc | Computationally-efficient traffic shaper |
20020004894, | |||
20030037096, | |||
EP710046, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Oct 18 2000 | TOMPKINS, JOSEPH B | Conexant Systems, Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 036430 | /0829 | |
Oct 18 2000 | LUSSIER, DANIEL J | Conexant Systems, Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 036430 | /0829 | |
Oct 18 2000 | SNYDER, WILSON P , II | Conexant Systems, Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 036430 | /0829 | |
Jun 27 2003 | Conexant Systems, Inc | MINDSPEED TECHNOLOGIES, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 036472 | /0592 | |
Dec 14 2007 | MINDSPEED TECHNOLOGIES, INC | CHEDMIN COMMUNICATION LTD , LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 036426 | /0603 | |
Aug 12 2015 | CHEDMIN COMMUNICATION LTD , LLC | F POSZAT HU, L L C | MERGER SEE DOCUMENT FOR DETAILS | 036684 | /0393 | |
Dec 15 2017 | F POSZAT HU, L L C | INTELLECTUAL VENTURES ASSETS 67 LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 044824 | /0286 | |
Jan 05 2018 | INTELLECTUAL VENTURES ASSETS 67 LLC | BICAMERAL LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 046688 | /0582 |
Date | Maintenance Fee Events |
Oct 11 2013 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Oct 16 2017 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
Date | Maintenance Schedule |
Feb 01 2014 | 4 years fee payment window open |
Aug 01 2014 | 6 months grace period start (w surcharge) |
Feb 01 2015 | patent expiry (for year 4) |
Feb 01 2017 | 2 years to revive unintentionally abandoned end. (for year 4) |
Feb 01 2018 | 8 years fee payment window open |
Aug 01 2018 | 6 months grace period start (w surcharge) |
Feb 01 2019 | patent expiry (for year 8) |
Feb 01 2021 | 2 years to revive unintentionally abandoned end. (for year 8) |
Feb 01 2022 | 12 years fee payment window open |
Aug 01 2022 | 6 months grace period start (w surcharge) |
Feb 01 2023 | patent expiry (for year 12) |
Feb 01 2025 | 2 years to revive unintentionally abandoned end. (for year 12) |