METHOD AND SYSTEM FOR EXTENDED STEERING TAGS (STAGS) TO MINIMIZE MEMORY BANDWIDTH FOR CONTENT DELIVERY SERVERS

• US 20080301311A1
• Filed: 11/16/2007
• Published: 12/04/2008
• Est. Priority Date: 05/30/2007
• Status: Active Grant

• Current Assignee: Avago Technologies General IP PTE Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Bestler, Caitlin
• Granted Patent: US 8,271,669 B2
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields

Abstract

Aspects of a method and system for extended steering tags (STags) to minimize memory bandwidth for content delivery servers are presented. Aspects of the system may include at least one processor that enables reception of at least a portion of a data stripe within a direct data placement (DDP) segment. The one or more processors may enable transfer of a modified version of the received portion of the data stripe to a client without waiting to receive a subsequent portion or more of a data stripe destined for the client. The modified version of the received portion or more of the data stripe may contain a destination location for storing the modified version of the portion or more of the data stripe within the client.

Claims

1. A method for handling data in a communications system, the method comprising:

receiving at least a portion of a data stripe within a direct data placement (DDP) segment; and

transferring a modified version of said received at least a portion of said data stripe to a client without waiting to receive a subsequent at least a portion of a data stripe destined for said client, wherein said modified version of said received at least a portion of said data stripe comprises a destination location for storing said modified version of said at least a portion of said data stripe within said client.

2. The method according to claim 1, wherein said received DDP segment comprises a splicing steering tag (STag).

3. The method according to claim 2, wherein said received DDP segment comprises a signature field that identifies said splicing STag.

4. The method according to claim 3, comprising determining said destination location for said modified version of said received at least a portion of said data stripe based on at least one of:

said splicing STag, a data stripe offset field, a physical buffer list (PBL), and a server mask field.

5. The method according to claim 4, comprising generating an aggregated offset field based on said destination location.

6. The method according to claim 5, wherein said transferred modified version of said received at least a portion of said data stripe comprises said aggregated offset field.

7. The method according to claim 1, comprising modifying a value for a last (L) flag bit in said received DDP segment when generating a modified DDP segment when said received DDP segment is a last of a plurality of received DDP segments and a transferred said modified DDP segment is not a last of a plurality of transferred DDP segments.

8. The method according to claim 1, wherein a value for an L flag bit in said received DDP segment is equal to a corresponding value for an L bit in a transferred modified DDP segment when said received DDP segment is a last of a plurality of received DDP segments and said transferred modified DDP segment is a last of a plurality of transferred DDP segments.

9. The method according to claim 1, wherein a value for an L flag bit in said received DDP segment is equal to a corresponding value for an L bit in a transferred modified DDP segment when said received DDP segment is not a last of a plurality of received DDP segments and said transferred modified DDP segment is not a last of a plurality of transferred DDP segments.

10. The method according to claim 1, wherein said client stores said modified version of said at least a portion of said data stripe based on said destination location.

11. A machine-readable storage having stored thereon, a computer program having at least one code section for handling data in a communications system, the at least one code section being executable by a machine for causing the machine to perform steps comprising:

receiving at least a portion of a data stripe within a direct data placement (DDP) segment; and

transferring a modified version of said received at least a portion of said data stripe to a client without waiting to receive a subsequent at least a portion of a data stripe destined for said client, wherein said modified version of said received at least a portion of said data stripe comprises a destination location for storing said modified version of said at least a portion of said data stripe within said client.

12. The machine-readable storage according to claim 11, wherein said received DDP segment comprises a splicing steering tag (STag).

13. The machine-readable storage according to claim 12, wherein said received DDP segment comprises a signature field that identifies said splicing STag.

14. The machine-readable storage according to claim 13, wherein said at least one code section comprises code for determining said destination location for said modified version of said received at least a portion of said data stripe based on at least one of:

said splicing STag, a data stripe offset field, a physical buffer list (PBL), and a server mask field.

15. The machine-readable storage according to claim 14, wherein said at least one code section comprises code for generating an aggregated offset field based on said destination location.

16. The machine-readable storage according to claim 15, wherein said transferred modified version of said received at least a portion of said data stripe comprises said aggregated offset field.

17. The machine-readable storage according to claim 11, wherein said at least one code section comprises code for modifying a value for a last (L) flag bit in said received DDP segment when generating a modified DDP segment when said received DDP segment is a last of a plurality of received DDP segments and a transferred said modified DDP segment is not a last of a plurality of transferred DDP segments.

18. The machine-readable storage according to claim 11, wherein a value for an L flag bit in said received DDP segment is equal to a corresponding value for an L bit in a transferred modified DDP segment when said received DDP segment is a last of a plurality of received DDP segments and said transferred modified DDP segment is a last of a plurality of transferred DDP segments.

19. The machine-readable storage according to claim 11, wherein a value for an L flag bit in said received DDP segment is equal to a corresponding value for an L bit in a transferred modified DDP segment when said received DDP segment is not a last of a plurality of received DDP segments and said transferred modified DDP segment is not a last of a plurality of transferred DDP segments.

20. The machine-readable storage according to claim 11, wherein said client stores said modified version of said at least a portion of said data stripe based on said destination location.

21. A system for handling data in a communications system, the system comprising:

at least one processor that enables reception of at least a portion of a data stripe within a direct data placement (DDP) segment; and

said at least one processor enables transfer of a modified version of said received at least a portion of said data stripe to a client without waiting to receive a subsequent at least a portion of a data stripe destined for said client, wherein said modified version of said received at least a portion of said data stripe comprises a destination location for storing said modified version of said at least a portion of said data stripe within said client.

22. The system according to claim 21, wherein said received DDP segment comprises a splicing steering tag (STag).

23. The system according to claim 22, wherein said received DDP segment comprises a signature field that identifies said splicing STag.

24. The system according to claim 23, wherein said at least one processor enables determination of said destination location for said modified version of said received at least a portion of said data stripe based on at least one of:

said splicing STag, a data stripe offset field, a physical buffer list (PBL), and a server mask field.

25. The system according to claim 24, wherein said at least one processor enables generation of an aggregated offset field based on said destination location.

26. The system according to claim 25, wherein said transferred modified version of said received at least a portion of said data stripe comprises said aggregated offset field.

27. The system according to claim 21, wherein said at least one processor enables modification of a value for a last (L) flag bit in said received DDP segment when generating a modified DDP segment when said received DDP segment is a last of a plurality of received DDP segments and a transferred said modified DDP segment is not a last of a plurality of transferred DDP segments.

28. The system according to claim 21, wherein a value for an L flag bit in said received DDP segment is equal to a corresponding value for an L bit in a transferred modified DDP segment when said received DDP segment is a last of a plurality of received DDP segments and said transferred modified DDP segment is a last of a plurality of transferred DDP segments.

29. The system according to claim 21, wherein a value for an L flag bit in said received DDP segment is equal to a corresponding value for an L bit in a transferred modified DDP segment when said received DDP segment is not a last of a plurality of received DDP segments and said transferred modified DDP segment is not a last of a plurality of transferred DDP segments.

30. The system according to claim 21, wherein said client stores said modified version of said at least a portion of said data stripe based on said destination location.