Data matching using flow based packet data storage

• US 8,929,380 B1
• Filed: 05/05/2014
• Issued: 01/06/2015
• Est. Priority Date: 08/02/2006
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Silver Peak Systems Incorporated (Hewlett-Packard Enterprise Company)
• Inventors: Hughes, David Anthony, Burns, John, Yin, Zhigang
• Primary Examiner(s): VU, HOANG-CHUONG Q
• Application Number:
  US14/270,101
• Time in Patent Office: 246 Days
• Field of Search: 370/392, 370/395.32, 370/389, 711/216, 707/205
• US Class Current: 370/392
• CPC Class Codes: H04L 43/062 related to network traffic
• CPC Class Codes: H04L 45/745 Address table lookup; Address filtering
• CPC Class Codes: H04L 47/2483 involving identification of individual flows
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 49/901 using storage descriptor, e.g. read or write pointers
• CPC Class Codes: H04L 49/9047 including multiple buffers, e.g. buffer pools
• CPC Class Codes: H04L 49/9057 Arrangements for supporting packet reassembly or resequencing
• CPC Class Codes: H04L 49/9094 Arrangements for simultaneous transmit and receive, e.g. simultaneous reading/writing from/to the storage element
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

A system for matching data using flow based packet data storage includes a communications interface and a processor. A communications interface receives a packet between a source and a destination. The processor identifies a flow between the source and the destination based on the packet. The processor determines whether some of packet data of the packet indicates a potential match to data in storage using hashes. The processor then stores the data from the most likely data match and second most likely data match without a packet header in a block of memory in the storage based on the flow.

Claims

1. A system for matching data using flow based packet data storage, the system comprising:

a communications interface that receives at least one data packet at a network device between a source and a destination, the at least one data packet including data and flow information; and

a processor that;

identifies a flow between the source and the destination based on the flow information in the at least one data packet;

determines whether at least a portion of the data from the received at least one data packet indicates a potential match to data in storage using hashes;

retrieves a list of possible data matches;

uses a computed hash index to index a hash table for the data;

determines match sizes of the most likely data match and second most likely data match;

stores the data from the at least one data packet without a packet header in a block of memory allocated for the flow if both match sizes are small; and

generates a retrieve instruction for the data match with the larger match size if at least one match size is not small.

2. The system of claim 1 wherein the processor moves the storage data between a fast memory and a slow memory.

3. The system of claim 1 wherein the flow comprises a session between the source and the destination.

4. The system of claim 1 wherein the processor retrieves a hash state of the hashes for the flow.

5. The system of claim 1 wherein the processor determines the hashes for the flow.

6. The system of claim 1 wherein the processor stores a hash state of the hashes for the flow.

7. The system of claim 1 wherein the processor updates the hash table with the hashes.

8. The system of claim 1 wherein the hashes are rolling.

9. The system of claim 1 wherein the processor allocates the block of memory for the identified flow.

10. The system of claim 1 wherein the processor transmits the at least one packet data.

11. The system of claim 1 wherein the block of memory allocated for the flow is allocated from a list of partially filled blocks of memory.

12. A method for matching data using flow based packet data storage, the method comprising:

receiving at least one data packet at a network device between a source and a destination, the at least one data packet including data and flow information;

identifying a flow between the source and the destination based on the flow information in the at least one data packet;

determining whether at least a portion of the data from the received at least one data packet indicates a potential match to data in storage using hashes;

retrieving a list of possible data matches;

using a computed hash index to index a hash table for the data;

determining match sizes of the most likely data match and second most likely data match;

storing the data from the at least one data packet without a packet header in a block of memory allocated for the flow, if both match sizes are small; and

generating a retrieve instruction for the data match with the larger match size, if at least one match size is not small.

13. The method of claim 12 further comprising moving the storage data between a fast memory and a slow memory.

14. The method of claim 12 wherein the flow comprises a session between the source and the destination.

15. The method of claim 12 further comprising retrieving a hash state of the hashes for the flow.

16. The method of claim 12 further comprising determining the hashes for the flow.

17. The method of claim 12 further comprising storing a hash state of the hashes for the flow.

18. The method of claim 12 further comprising updating the hash table with the hashes.

19. The method of claim 12 wherein the hashes are rolling.

20. The method of claim 12 further comprising allocating the block of memory for the identified flow.

21. The method of claim 12 further comprising transmitting the at least one packet data.

22. The method of claim 12 further comprising:

allocating the block of memory for the identified flow from a list of partially filled blocks of memory.

23. A software product for processing packets, the software product comprising:

software operational when executed by a processor to direct the processor to receive at least one data packet at a network device between a source and a destination, the at least one data packet including data and flow information, to identify a flow between the source and the destination based on the flow information in of the at least one data packet, to determine whether at least a portion of the data from the received at least one data packet indicates a potential match to data in storage using hashes, to retrieve a list of possible data matches, use a computed hash index to index a hash table for the data, to determine match sizes of the most likely data match and second most likely data match, to store the data from the at least one data packet without a packet header in the block of memory allocated for the flow if both match sizes are small, and to generate a retrieve instruction for the data match with the larger match size if at least one match size is not small; and

a non-transitory computer-readable storage medium configured to store the software.

24. The software product of claim 23 wherein the software is operational when executed by the processor to direct the processor to move the storage data between a fast memory and a slow memory.

25. The software product of claim 23 wherein the flow comprises a session between the source and the destination.

26. The software product of claim 23 wherein the software is operational when executed by the processor to direct the processor to retrieve a hash state of the hashes for the flow.

27. The software product of claim 23 wherein the software is operational when executed by the processor to direct the processor to determine the hashes for the flow.

28. The software product of claim 23 wherein the software is operational when executed by the processor to direct the processor to store a hash state of the hashes for the flow.

29. The software product of claim 23 wherein the software is operational when executed by the processor to direct the processor to update the hash table with the hashes.

30. The software product of claim 23 wherein the hashes are rolling.

31. The software product of claim 23 wherein the software is operational when executed by the processor to direct the processor to allocate the block of memory for the identified flow.

32. The software product of claim 23 wherein the software is operational when executed by the processor to direct the processor to transmit the packet data.

33. The software product of claim 23 wherein the block of memory allocated for the flow is allocated from a list of partially filled blocks of memory.