Packet processing system, method and device utilizing a port client chain

US12298925B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12298925-B2
Application numberUS-202318105741-A
CountryUS
Kind codeB2
Filing dateFeb 3, 2023
Priority dateMar 30, 2015
Publication dateMay 13, 2025
Grant dateMay 13, 2025

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A packet processing system having each of a plurality of hierarchical clients and a packet memory arbiter serially communicatively coupled together via a plurality of primary interfaces thereby forming a unidirectional client chain. This chain is then able to be utilized by all of the hierarchical clients to write the packet data to or read the packet data from the packet memory.

First claim

Opening claim text (preview).

We claim: 1. A packet processing system comprising: a non-transitory computer-readable packet memory organized into one or more memory banks; a packet memory arbiter coupled with the one or more memory banks of the packet memory; and a plurality of hierarchical clients, wherein one or more of the hierarchical clients are configured to transmit requests to access the packet memory to the packet memory arbiter, wherein each request of the requests includes a request tag that identifies the hierarchical client that transmitted the request. 2. The system of claim 1 , wherein the plurality of hierarchical clients are each associated with a plurality of system ports and arbitrate between requests to access the packet memory from the plurality of system ports. 3. The system of claim 2 , wherein the hierarchical clients and the packet memory arbiter form a unidirectional client chain and the unidirectional client chain is only used to transmit the packet data to be read out from the packet memory and the packet memory arbiter is at the beginning of the unidirectional client chain. 4. The system of claim 2 , wherein the unidirectional client chain includes the packet memory arbiter and the unidirectional client chain is used both to transmit the packet data to be read out from the packet memory and to transmit the packet data to be written into the packet memory, and further wherein the unidirectional client chain forms a loop such that the packet memory arbiter is at the beginning and the end of the unidirectional client chain. 5. The system of claim 2 , wherein the unidirectional client chain includes the packet memory arbiter and the unidirectional client chain is only used to transmit the packet data to be written into the packet memory and the packet memory arbiter is at the end of the unidirectional client chain. 6. The system of claim 5 , wherein one or more of the plurality of hierarchical clients are directly coupled to the packet memory arbiter separately from the unidirectional client chain via one or more secondary interfaces, and further wherein the secondary interfaces are only used to transmit the packet data to be read out from the packet memory. 7. The system of claim 6 , wherein the unidirectional client chain further comprises one or more write clients that are configured to write the packet data into the packet memory. 8. The system of claim 7 , further comprising a plurality of additional system ports that are each associated with one of a plurality of additional hierarchical clients, wherein each of the plurality of additional hierarchical clients and the packet memory arbiter are serially communicatively coupled together via a plurality of additional interfaces thereby forming an additional unidirectional client chain, and further wherein all of the plurality of additional hierarchical clients write the packet data to or read the packet data from the packet memory via the additional unidirectional client chain. 9. The system of claim 8 , wherein each cycle the packet memory arbiter is configured to limit a sum of a number of the plurality of system ports and a number of the plurality of additional system ports that are granted access to write the packet data into the one or more memory banks of the packet memory such that the sum is equal to or less than a number of write ports of the one or more memory banks. 10. The system of claim 9 , wherein the additional unidirectional client chain and the unidirectional client chain have substantially the same latency. 11. The system of claim 10 , wherein the primary interfaces and the secondary interfaces are wide interfaces having a large bandwidth. 12. The system of claim 1 , wherein after granting one of the requests, the packet memory arbiter transmits a return tag to the hierarchical client that sent the request, wherein the return tag identifies the hierarchical client that sent the request, and further wherein the return tag indicates to the hierarchical client that sent the request when to write packet data to or read packet data from the unidirectional client chain. 13. A packet memory arbiter stored on a non-transitory computer-readable memory, wherein the packet memory arbiter is configured to: receive a plurality of requests sent by a plurality of hierarchical clients to access memory banks of a packet memory, wherein each of the requests include a request tag that identifies the hierarchical client that transmitted the request; and arbitrate between the plurality of requests by granting one of the requests. 14. The packet memory arbiter of claim 13 , wherein each of the plurality of hierarchical clients and the packet memory arbiter are serially communicatively coupled together via a plurality of primary interfaces thereby forming a unidirectional client chain. 15. The packet memory arbiter of claim 14 , wherein the packet memory arbiter is further configured to at least one of: receive via the unidirectional client chain packet data that is to be written into the packet memory from the plurality of hierarchical clients, and output via the unidirectional client chain packet data that is to be read out from the packet memory to the plurality of hierarchical clients. 16. The packet memory arbiter of claim 15 , wherein the plurality of hierarchical clients arbitrate between requests to access the packet memory from a plurality of system ports. 17. The packet memory arbiter of claim 16 , wherein the unidirectional client chain is only used to transmit the packet data to be read out from the packet memory and the packet memory arbiter is at the beginning of the unidirectional client chain. 18. The packet memory arbiter of claim 16 , wherein the unidirectional client chain is used both to transmit the packet data to be read out from the packet memory and to transmit the packet data to be written into the packet memory, and further wherein the unidirectional client chain forms a loop such that the packet memory arbiter is at the beginning and the end of the unidirectional client chain. 19. The packet memory arbiter of claim 16 , wherein the unidirectional client chain is only used to transmit the packet data to be written into the packet memory and the packet memory arbiter is at the end of the unidirectional client chain. 20. The packet memory arbiter of claim 19 , wherein one or more of the plurality of hierarchical clients are directly coupled to the packet memory arbiter separately from the unidirectional client chain via one or more secondary interfaces, and further wherein the secondary interfaces are only used to transmit the packet data to be read out from the packet memory. 21. The packet memory arbiter of claim 20 , wherein the unidirectional client chain further comprises one or more write clients that are configured to write the packet data into the packet memory. 22. The packet memory arbiter of claim 21 , wherein a plurality of additional system ports are each associated with one of a plurality of additional hierarchical clients, and further wherein each of the plurality of additional hierarchical clients and the packet memory arbiter are serially communicatively coupled together via a plurality of additional interfaces thereby forming an additional unidirectional client chain, and further wherein all of the plurality of additional hierarchical clients write the packet data to or read the packet data from the packet memory via the additional unidirectional client chain. 23. The packet memory arbit

Assignees

Inventors

Classifications

  • minimising geographical or physical path length · CPC title

  • using dynamic buffer space allocation · CPC title

  • using buffers · CPC title

  • using switching circuits, e.g. switching matrix, connection or expansion network (G06F13/4009 takes precedence) · CPC title

  • with latency improvement · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12298925B2 cover?
A packet processing system having each of a plurality of hierarchical clients and a packet memory arbiter serially communicatively coupled together via a plurality of primary interfaces thereby forming a unidirectional client chain. This chain is then able to be utilized by all of the hierarchical clients to write the packet data to or read the packet data from the packet memory.
Who is the assignee on this patent?
Marvell Asia Pte Ltd
What technology area does this patent fall under?
Primary CPC classification G06F13/1663. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue May 13 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 7 related publications on this page (citations in our corpus or others sharing the same primary CPC).