Abstract:
A method for inline bus data compression and decompression is disclosed. In one embodiment, data is selected for transfer via a data bus, the data is divided into byte sized divisions of the bus width, and each byte is compressed by an individual compression engine. The data is then properly sequenced, aligned and recombined and further transmitted in its compressed state. When required to be decompressed, the compressed data is again divided into bytes of compressed data, each byte being decompressed individually, and then restored to the bus in its uncompressed form, in essence, in the reverse order of the compression process.

Description:
FIELD OF THE INVENTION  
         [0001]    The present invention relates to the field of computer memory management. Specifically, the present invention relates to a method and system for improving inline compression and decompression in computer bus operations.  
         BACKGROUND OF THE INVENTION  
         [0002]    As the gap between hard drive access time and memory access time increases, it is increasingly desirable to locate more data in memory. This is increasingly important because the size of applications and data sets are increasing at a faster rate than the density of main memory. Furthermore, systems with multiprocessors may have many programs running simultaneously with each program having a relatively small number of pages of instructions and data in main memory. Hence, page faults may occur frequently. One way to increase the effective storage capacity of main memory is to compress its contents. However, conventional computer systems may be unable to efficiently manage the compressed data in main memory.  
           [0003]    In typical computer operations, data is in near-constant motion in and out of memory; between memory and processors or between other sources and destinations. As computers have gotten faster, the speed demands of compression/decompression engines have increased enormously.  
           [0004]    Most conventional compression engines are capable of operating at data bus speeds but not at the bandwidth of, for example, a modern memory bus. This limitation slows down memory bus operations by adding latency to each transaction. A number of techniques have been employed to work around the speed loss associated with both compression and decompression.  
           [0005]    One common technique uses multiple compression/decompression engines which are each fed pieces of any given memory packet. Typically, the packet pieces are equally sized and very large, commonly on the order of one kilobyte or even larger. These large data “chunks” emerge from the compression engine at roughly the same compression ratio but with significant lag in comparison to bus speed. The piece sizes can vary from transaction to transaction, causing the compression engines to almost never be used at full efficiency and, more importantly, the size of compressed data blacks varies with every transaction, putting huge demands on buffers and significantly reducing overall speed.  
           [0006]    What is needed then, is a means of inline compression/decompression of data transmitted in computer buses that fully exploits the speed of available compression engines and exerts minimal impact on the speed and bandwidth of bus transactions as well as minimizing increased complexity of bus structures. A further need exists for such a means to efficiently use resources, such as the memory required for a table specifying the locations of the compressed data and on the compression/decompression engines themselves.  
         SUMMARY OF THE INVENTION  
         [0007]    The present invention provides a method for the inline compression and decompression of data transmitted in computer buses that fully exploits the speed of available compression engines and exerts minimal impact on the speed and bandwidth of bus transactions. In addition, the implementation of embodiments of the disclosed invention minimize the need for increased complexity of bus structures. Furthermore, the disclosed invention can allow the efficient use of resources, such as the memory required for a table specifying the locations of the compressed data and efficient use of the compression/decompression engines themselves.  
           [0008]    A method for inline bus data compression and decompression is disclosed. In one embodiment, data is selected for transfer via a data bus, the data is divided into byte sized divisions of the bus width, and each byte is compressed by an individual compression engine. The data is then properly sequenced, aligned and recombined and further transmitted in its compressed state. When required to be decompressed, the compressed data is again divided into bytes of compressed data, each byte being decompressed individually, and then restored to the bus in its uncompressed form, in essence, in the reverse order of the compression process.  
           [0009]    These and other objects and advantages of the present invention will become obvious to those of ordinary skill in the art after having read the following detailed description of the preferred embodiments which are illustrated in the various drawing figures.  
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0010]    The operation of this invention can be best visualized by reference to the drawings.  
         [0011]    [0011]FIG. 1 illustrates a typical computer and bus architecture in accordance with one embodiment of the present invention.  
         [0012]    [0012]FIG. 2 illustrates a typical inline data compression/decompression operation in accordance with one embodiment of the present invention.  
         [0013]    [0013]FIG. 3 illustrates a memory bus inline compression/decompression operation in accordance with one embodiment of the present invention.  
         [0014]    [0014]FIG. 4 illustrates a memory bus inline compression/decompression operation in accordance with one embodiment of the present invention.  
     
    
     SPECIFICATION  
       [0015]    Reference will now be made in detail to the preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings. While the invention will be described in conjunction with the preferred embodiments, it will be understood that they are not intended to limit the invention to these embodiments. On the contrary, the invention is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the invention as defined by the appended claims. Furthermore, in the following detailed description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be obvious to one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the present invention. Some portions of the detailed descriptions that follow are presented in terms of procedures, logic blocks, processing, and other symbolic representations of operations on data bits within a computer. These descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. A procedure, logic block, process, etc., is here, and generally, conceived to be a self-consistent sequence of steps or instructions leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a computer system. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, bytes, values, elements, symbols, characters, terms, numbers, or the like.  
         [0016]    It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present invention, discussions utilizing terms such as “setting,” “storing,” “scanning,” “receiving,” “sending,” “disregarding,” “entering,” or the like, refer to the action and processes of a computer system or similar intelligent electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system&#39;s registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission  
       DETAILED DESCRIPTION  
       [0017]    This discussion of this embodiment of the present invention addresses inline compression/decompression of computer data. Inline compression/decompression is accomplished while data is en route in a computer bus. In typical computer operations, data is in near-constant motion in and out of memory, between memory and processors or between other sources and destinations. As processing speeds have increased, the demand for speed of memory input and output (I/O) compression/decompression engines has also increased, enormously.  
         [0018]    Compression is now being used for wide high speed buses such as memory buses. The only way to avoid delays when performing compression on a memory bus, of course, is to do so at bus speeds. Most conventional compression/decompression engines are capable of operating at data bus speeds but not at the bandwidth of a modern data bus. This limitation slows down data bus operations and a number of techniques have been employed to work around the speed loss associated with both compression and decompression.  
         [0019]    Typical implementations of compression/decompression engines are as hardware devices that operate between source and destination devices. They can be completely autonomous or they can be controlled by the operating system (OS). An understanding of these concepts and others presented in this embodiment of the present invention can best be understood by reference to the figures.  
         [0020]    [0020]FIG. 1 illustrates a typical computer system. As shown, a general purpose computer,  100 , comprises bus  150 , connecting processor  101 , non-volatile ROM  102 , RAM  103  and some form of data storage  104 , all contained within optional enclosure  100 . The computer also likely comprises an optional display device  105 , some form of user input such as keyboard  106  and cursor control  107  and possibly other signal input/output circuits  108 . Compression/decompression may be handled by dedicated hardware engine  110 . If compression and decompression are controlled by software, that software is likely to be resident in ROM  102  or in the OS loaded into memory from data storage device  104 .  
         [0021]    Another possible arrangement, in this embodiment of the present invention, is the possible placement of compression/decompression engine  110  in series with RAM  103 ′ bus connection. However placed, the inline compression/decompression concepts presented here are the same.  
         [0022]    [0022]FIG. 2 illustrates a typical inline compression/decompression technique that uses a single compression/decompression engine,  201 , to process data blocks being transmitted in a bus. Because typical compression engines can best process a small block of data at any one time, data associated with any particular transaction is fragmented into “digestible” pieces. Most compression/decompression engines perform best processing a single byte of data at a time. Since bus transactions are rarely one byte in width, typical schemes buffer the data to be compressed/decompressed and then perform the compression/decompression as a separate operation independent of the bus. The resulting data is them stored in yet another buffer before being sent to its destination. This is not the best solution since it adds a long latency before compression/decompression is not performed at bus speeds.  
         [0023]    Previous architectures, when a data block to be compressed/decompressed is too large in size, have reduced the size of the block by dividing the data by successive factors of two. Reducing the size of the data block reduces the latency of compression/decompression when trying to find a small amount of data, since only the section of the original data block with the requested data must be compressed or decompressed.  
         [0024]    A common compression/decompression technique that uses multiple compression engines feeds each engine a piece of any given data packet. Typically, the packet pieces are of equal size and emerge from the compression engine at roughly the same compression ratio. Unfortunately, as in common techniques using a single engine, the compressed data piece sizes vary and the compression engines are almost never used at full efficiency. Furthermore, compression and decompression both add varying latency with larger processed data blocks, increasing the demand on buffering to maintain proper sequencing and alignment in the engines&#39; output. The embodiment of the present invention discussed here presents two methods describing inline compression/decompression that use multiple parallel compression engines and allow the operations to occur at high bus speeds with minimal buffering and latency in each transaction.  
         [0025]    Most modern hardware compression engines operate most efficiently when fed a byte-sized data block for each compression operation, much smaller than is typically employed by modern buses. FIGS. 3 and 4 illustrate two different methods of in-line compression/decompression without reducing memory bus bandwidth. The examples shown in the figures are for a four-byte-wide bus, but can be used for any bus width. An important concept presented in this embodiment of the present invention is that, instead of dividing a packet into equal pieces in a large scale, the packet can be divided into equal size pieces along byte boundaries. Existing compression engines can work at bus speed, but only a width of one byte.  
         [0026]    [0026]FIG. 3 illustrates the operation of parallel compression engines that each compress a single byte of the bus bandwidth at a time in any compression transaction. Bytes are most commonly eight bits in length. A 32 bit bus width would thus require four compression engines to continuously compress one byte at a time and a 64 bit wide bus would require eight compression engines. In FIG. 3, compression engines  301 - 304  are shown each being fed a single byte of a four byte wide (32 bit) data bus data transaction (t 1 , t 2 , etc.). It must be noted here that the transaction may be thousands of bytes long. In the example in FIG. 3, each engine processes every fourth byte of bus width. Engine  303 , for example, processes bytes  2  and  6  of transaction t 1 . Decompression would work, essentially, in the reverse.  
         [0027]    After compression, the resultant data, in this embodiment, is dependant upon the incoming data (t 1 , t 2 , t 3 , t 4 , etc.) and the compression algorithm used. The example in FIG. 3 shows a 2:1 compression ratio. This means that bytes  2  of compressed data blocks C 1  and C 2  contain the compressed data from byte  2  of t 1 , t 2 , t 3 , and t 4 . As each byte emerges, from the compression engine (C 1 , C 2 , etc.) it must be properly sequenced and aligned in buffers so that the transaction placed on the bus contains the full bus width of data. This means that there may be some bus cycles where there is no data on the bus at the output of the compressors since compressed data produces fewer bytes to be transferred. Therefore, the incoming uncompressed data is allowed to operate at full bus bandwidth, but the outgoing compressed data operates at the bus bandwidth divided by the compression ratio; at one half bus bandwidth in the example.  
         [0028]    [0028]FIG. 3 further shows each byte width of the bus feeding one compressor/decompressor. For this example, this means every fourth byte is compressed by each compression engine. This slows down the response time of the bus by only the latency of the compression engine, and does not decrease bandwidth. Since the compressor is working at bus speeds, no buffering is required of data before it is compressed. However, a small amount of buffering is required at the output of the compressor to make sure that each compressor places one byte on the bus at the same time. This is required because there are fewer bytes at the output of a compressor than at the input and the compressed bytes need to be aligned to guarantee correct, coordinated, decompression.  
         [0029]    Decompression, in this embodiment of the present invention, would be effected in the reverse process of compression. A small amount of buffering would be required to properly sequence and align compressed data prior to decompression. Since some realignment might be required after decompression, some downstream buffering might be required there, as well.  
         [0030]    [0030]FIG. 4 illustrates another method for use of multiple compression engines that reduces added latency. Here, each memory bus transaction (t 1 , t 2 , etc) is fed, in byte-sized blocks, to only one compression engine,  401 ,  402 , etc. Compression is accomplished by bus transaction. Each compressor is fed the number of bytes supported by the bus width. This requires buffering of one or two transactions for each compressor in order to operate at full bus speeds and possibly has a more complicated bus connection. While this method may show some advantages for complicated bus structures, in most cases the better method is the one shown in FIG. 3.  
         [0031]    The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed, and obviously many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims appended hereto and their equivalents.