DEFLATE FILE DATA OPTIMIZATION

• US 20090240718A1
• Filed: 03/21/2008
• Published: 09/24/2009
• Est. Priority Date: 03/21/2008
• Status: Active Grant

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Ocarina Networks, Inc. (Dell Technologies Inc.)
• Inventors: Brueggemann, Eric, Rao, Goutham
• Granted Patent: US 8,516,002 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]

Abstract

Mechanisms are provided for optimizing file data compressed using deflate mechanisms such as the ZLIB Compressed Data Format Specification and the DEFLATE Compressed Data Format Specification. Deflate mechanisms output different deflate file data depending on specific file data parameters. An optimization tool decompresses the deflate file data and outputs an optimized data stream. When a client application attempts to access the deflate data, the tool deoptimizes the optimized data stream and applies the same deflate algorithm to generate deflate file data. Although the deflate algorithm is applied without using the file data parameters used to generate the original deflate file data, substitute deflate file data is produced.

Claims

1. A method, comprising:

decompressing deflate file data corresponding to file data compressed using a plurality of file data parameters and a deflate algorithm, wherein the deflate file data is decompressed to obtain the file data;

optimizing the file data to generate optimized file data, the optimized file data having a optimized file data length less than the deflate file data length;

receiving a request to access the deflate file data;

deoptimizing the optimized file data to obtain the file data;

compressing the file data using the deflate algorithm without access to the plurality of file data parameters to generate substitute deflate file data.

2. The method of claim 1, wherein the deflate algorithm generates a deflate file data stream.

3. The method of claim 2, wherein generating substitute deflate file data comprises flushing the deflate file data stream to a byte boundary.

4. The method of claim 1, wherein generating substitute deflate file data comprises adding bytes to the deflate file data stream so that the substitute deflate file data stream length is the same as the deflate file data length.

5. The method of claim 4, wherein generating substitute deflate file data comprises adding a plurality of padding markers provided with a deflate algorithm specification.

6. The method of claim 5, wherein the padding markers include empty static and empty stored blocks used for a corresponding inflate algorithm.

7. The method of claim 1, wherein the request is received from an application server connected to a Network Attached Storage (NAS) system.

8. The method of claim 7, wherein the plurality of file data parameters include a window size, a custom dictionary, and a memory level.

9. An apparatus, comprising:

means for decompressing deflate file data corresponding to file data compressed using a plurality of file data parameters and a deflate algorithm, wherein the deflate file data is decompressed to obtain the file data;

means for optimizing the file data to generate optimized file data, the optimized file data having a optimized file data length less than the deflate file data length;

means for receiving a request to access the deflate file data;

means for deoptimizing the optimized file data to obtain the file data;

means for compressing the file data using the deflate algorithm without access to the plurality of file data parameters to generate substitute deflate file data.

10. The apparatus of claim 9, wherein the deflate algorithm generates a deflate file data stream.

11. The apparatus of claim 10, wherein generating substitute deflate file data comprises flushing the deflate file data stream to a byte boundary.

12. The apparatus of claim 9, wherein generating substitute deflate file data comprises adding bytes to the deflate file data stream so that the substitute deflate file data stream length is the same as the deflate file data length.

13. The method of claim 12, wherein generating substitute deflate file data comprises adding a plurality of padding markers provided with a deflate algorithm specification.

14. The method of claim 13, wherein the padding markers include empty static and empty stored blocks used for a corresponding inflate algorithm.

15. A computer readable medium having computer code embodied therein, the computer readable medium comprising:

computer code for decompressing deflate file data corresponding to file data compressed using a plurality of file data parameters and a deflate algorithm, wherein the deflate file data is decompressed to obtain the file data;

computer code for optimizing the file data to generate optimized file data, the optimized file data having a optimized file data length less than the deflate file data length;

computer code for receiving a request to access the deflate file data;

computer code for deoptimizing the optimized file data to obtain the file data;

computer code for compressing the file data using the deflate algorithm without access to the plurality of file data parameters to generate substitute deflate file data.

16. The computer readable medium of claim 15, wherein the deflate algorithm generates a deflate file data stream.

17. The computer readable medium of claim 16, wherein generating substitute deflate file data comprises flushing the deflate file data stream to a byte boundary.

18. The computer readable medium of claim 15, wherein generating substitute deflate file data comprises adding bytes to the deflate file data stream so that the substitute deflate file data stream length is the same as the deflate file data length.

19. The computer readable medium of claim 18, wherein generating substitute deflate file data comprises adding a plurality of padding markers provided with a deflate algorithm specification.

20. The computer readable medium of claim 19, wherein the padding markers include empty static and empty stored blocks used for a corresponding inflate algorithm.