Abstract:
An embodiment of the present invention includes a nonvolatile memory system comprising nonvolatile memory for storing sector information, the nonvolatile memory being organized into blocks with each block including a plurality of sectors, each sector identified by a logical block address and for storing sector information. A controller is coupled to the nonvolatile memory for writing sector information to the latter and for updating the sector information, wherein upon updating sector information, the controller writes to the next free or available sector(s) of a block such that upon multiple re-writes or updating of sector information, a plurality of blocks are substantially filled with sector information and upon such time, the controller rearranges the updated sector information in sequential order based on their respective logical block addresses thereby increasing system performance and improving manufacturing costs of the controller.

Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
   This application is a continuation-in-part of my U.S. patent application Ser. No. 09/620,544, filed on Jul. 21, 2000 now U.S. Pat. No. 6,978,342 issued on Dec. 20, 2005 and entitled “Moving Sectors Within a Block of Information In a Flash Memory Mass Storage Architecture”, the disclosure of which is incorporated herein by reference as though set forth in full. 

   BACKGROUND OF THE INVENTION 
   1. Field of the Invention 
   The present invention relates generally to methods and apparatus for improving the performance of file management within nonvolatile memory devices and particularly to increasing the speed of writing or storing information to such nonvolatile memory devices. 
   2. Description of the Prior Art 
   Various prior art methods and techniques were used to manage files, i.e. store data and read back data, within nonvolatile memory devices. Generally, a host device commands a controller, coupled between the host device and nonvolatile memory, to store certain information within nonvolatile memory and later to read the same. Such information depends on the application of the nonvolatile memory device. For example, in the case of digital cameras, digital pictures or photos is the information stored and retrieve from nonvolatile memory. In the case of Personal Computers (PCs), information is stored and retrieved from hard disk. 
   Since information is typically organized in sectors, each sector including a predetermined number of user data and a predetermined number of overhead data, the host commands the controller to store sector information by referencing addresses associated with particular sectors. For example, there may be sectors  0  through N and each group of sectors may define a block which would also have an address associated therewith for identifying the same. The controller uses sector addresses to organize digital information within the nonvolatile memory device. 
   In one prior art technique, as a part of file management of nonvolatile memory, when the host device commands the controller to write or store information to one or more particular sectors, identified by logical block addresses (LBAs), the controller writes to physical block addresses (PBAs) in the nonvolatile memory. Each block includes a very large amount of nonvolatile memory space, for example, 64 Kbytes. When a particular sector is updated or re-written thereto in nonvolatile memory, the controller writes the updated sector information to another location within the 64 Kbyte block space. To keep track of the current sector information, flags and address information are utilized and are updated by the controller to reflect the status of the sector. U.S. Pat. No. 5,341,330, issued on Aug. 23, 1994 to Wells et al. and entitled “Method For Writing to a Flash Memory Array During Erase Suspend Intervals” is an example of the teachings of such prior art technique. In the case where a particular sector is updated within a block, the sector location including previous information is marked ‘old’ utilizing a flag and the new or current sector location is marked ‘new’. Finally, when the block is full, i.e. no free or available location remains, a new block is used to store further updates to sectors and the old block is eventually erased prior to being re-utilized. 
   An example of the above discussion is perhaps better shown by reference to the example of  FIG. 1  depicting a block  10  and a block  12 , each of which include 64 Kbytes of storage area organized into sector locations for storing sector information. The number of sector locations included within a block is a function of the size of each sector. In the case, for example, where each sector includes 512 bytes, the number of sectors included within a block having 64 Kbytes is obviously 64×1024 divided by 512 or 128. 
   Referring still to  FIG. 1 , when the host writes to a sector location identified by LBA  0 , the controller stores said information into  14  and associated flag(s) are set to ‘new’ the first time such a write or store operation takes place after erasure of the block  10 . However, after following writes to the same sector, eventually, sector  0  at  14  will be set to ‘old’ indicating that the information stored therein is no longer current and that the controller should read another location to obtain the latest sector  0  information. This occurs when sector  0  is re-written or updated a following time and because information at  14  cannot be re-written without the block  10  first being erased. Since no erasure of block  10  has taken place, the next time sector  0  is written, its information will be placed at  28  and while the flag for location  14  will be set to ‘old’, the flag for location  28  is set to ‘new’ indicative of the most up-to-date sector  0  information until the latter is again updated, at which time the current information is stored for location  44  in block  10  and the flag at  44  is set to ‘new’ while the flag for location  28  is set to ‘old’. 
   The scenario described above applies to the writing or updating of all other sectors. By brief way of example, sector information identified by LBA  1 , is initially written at  16  and the next time it is written, it is written to the next available location in Block  10  which is location  30  and the following time after that when it is written by the host, it is written at  36  and the flags of  16 ,  30  and  36  are updated as describe above. This process continues until the block  10  becomes full at which time a new, or available, or free block is found by the controller, in this case, block  12 . From thereon, updated sector information is written to the block  12 , not only this, but at some point, if necessary, all sector locations including current sector information are moved to the block  12 , as explained in U.S. Pat. No. 5,341,330. 
   For example, in  FIG. 1 , after the first time when the sector identified by LBA  50  is written, assuming the host commands the controller to write to LBA  50  a next time and the block  10  is found to be full, the re-writing of sector  50  takes place within the block  12  rather than the block  10 . In fact, the re-written sector  50  information is written at  50  and all other sectors designated as having current or ‘new’ sector information are moved to the block  12 . This includes the sector identified by LBA  901 , which is at  24  in block  10  and moved to  52  in block  12 , the sector identified by LBA  902 , which is at  26  in block  10  and moved to  54  in block  12 , the sector identified by LBA  900 , which is at  34  in block  10  and moved to  56  in block  12  (note that this sector was initially written at  22  but the sector information at  22  is now ‘old’ and the most recent information resides at  34 , which is the reason for moving the information stored at  34  rather than the information at  22 ), the sector identified by LBA  1 , which is at  36  in block  10  and moved to  58  in block  12  and so on. 
   The above prior art technique is described in further detail in U.S. patent No. 6,978,342, on Dec. 20, 2005 and entitled “Moving Sectors Within a Block of Information In a Flash Memory Mass Storage Architure”, the disclosure of which is incorporated herein by reference as though set forth in full. The problem with this technique is that to move all of the sectors including current information to another new block is time-consuming and therefore a performance hindrance. This problem is even further exaggerated when using smaller block sizes as there are more numerous move operations with smaller block sizes and smaller block sizes are more prevalent by today&#39;s users of nonvolatile memory devices. 
   In the patent document referred to hereinabove, a method and apparatus is introduced for improving the performance of managing files or data within nonvolatile memory by organizing the memory into smaller block sizes and introducing a virtual logical block address (VLBA) to PBA relationship and a unique VLBA was assigned to each block and within each VLBA were sectors arranged in sequential order for decreasing the number of moves to expedite or improve the performance of the system through the use of mapping of PBAs to VLBAs. This VLBA to PBA mapping caused the size of the space manager within the controller device to decrease thereby resulting in a less expensive manufacturing of the controller device. However, in this method, it is presumed that sectors are written in sequential order by the host, if this is not the case, there is much wasted memory space. 
   In further explanation of prior art techniques,  FIG. 1(   a ) shows another method for updating sector information in that when sector information is re-written by a host, the new or updated information need be written to a free block. For example, as shown in  FIG. 1(   a ), when sector information, identified by LBA  0  in Block  0 , is re-written or updated, the updated LBA  0  sector information is written to LBA  0  of Block  1 . All other sectors within the Block  0  need then be moved to Block  1 . Accordingly, every time there is a re-write or update of a sector, an entire block of information is moved to a new or free block. Obviously, this adversely affects system performance because every time there is a re-write of a sector, a new location within a free block is written thereto while the old information remains in the previous block until the system erases the latter. 
   In yet another prior art technique, sectors are not moved necessarily right away after every sector information update, rather, re-writes and move operations are kept track thereof and when a block is full or nearly full of mostly old sector information, its current sector information is then moved to a new block. For example, as shown in  FIG. 1(   b ), when sector information to LBA  0  is updated, it is written to an available sector location in an available or free block but the remaining sectors of the previous block are not moved to the new block. Thus the previous block continues to hold some current sector information as well as some old sector information. The system keeps track of rewrites so that it has knowledge of which sectors are old and which are current and when a block is full or nearly full of old sector information, it moves the current sector information, if any, to the new of available block. 
   Thus, the need arises for a system and method for file or data management of information that is organized into sectors within nonvolatile memory devices while improving the performance for doing the same in an inexpensive manner. 
   SUMMARY OF THE INVENTION 
   Briefly, an embodiment of the present invention includes a nonvolatile memory system comprising nonvolatile memory for storing sector information, the nonvolatile memory being organized into blocks with each block including a plurality of sectors, each sector identified by a logical block address and for storing sector information. A controller is coupled to the nonvolatile memory for writing sector information to the latter and for updating the sector information, wherein upon updating sector information, the controller writes to the next free or available sector(s) of a block such that upon multiple re-writes or updating of sector information, a plurality of blocks are substantially filled with sector information and upon such time, the controller rearranges the updated sector information in sequential order based on their respective logical block addresses thereby increasing system performance and improving manufacturing costs of the controller. 
   The foregoing and other objects, features and advantages of the present invention will be apparent from the following detailed description of the preferred embodiments which make reference to several figures of the drawing. 

   
     IN THE DRAWINGS 
       FIG. 1  shows an example of a prior art technique for moving sector information upon re-write or updating operations. 
       FIG. 1(   a ) shows another example of a prior art technique for moving sector information upon re-write or updating operations. 
       FIG. 1(   b ) shows yet another example of a prior art technique for moving sector information upon re-write or updating operations. 
       FIG. 2  shows an example of the organization of information within nonvolatile memory devices is shown, in accordance with an embodiment of the present invention. 
       FIG. 3  illustrates the notion of finding free blocks by the controller and using the same for re-arranging sector information in accordance with a method of the present invention. 
       FIG. 4  further expands on the example of  FIG. 2 . 
   

   DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
   Referring now to  FIG. 2 , an example of the organization of information within nonvolatile memory devices is shown, in accordance with an embodiment of the present invention, to include M number of blocks  100 , M being an integer with each block including sector information. As will be apparent shortly, the blocks  100  are temporary locations for storage of sector information commanded to be written by the host through a controller device. The blocks  100  are shown to include Block N, Block N+M and Block N+M−1, wherein N is also an integer number. The reason for the notation N is to emphasize that Block N and in fact Blocks N+M and N+M−1 can be any one of the blocks within a nonvolatile memory. In one embodiment of the present invention, four blocks are designated as the blocks within  100  and thus temporary locations for storing data or information received from the host but in other embodiments of the present invention, any number of blocks may be employed. 
   In one embodiment of the present invention, each block includes 8 sectors but again, any number of sectors may be assigned to a block without departing from the scope and spirit of the present invention. Thus, in  FIG. 2 , Block N includes eight sector locations, as does Block N+M and Block N+M−1. In the example of  FIG. 2 , when the host initially writes a sector identified by the LBA  0 , this information is placed in the first sector location of Block N, at  102 . Next, if the host writes information to a sector identified by LBA  1 , this information is placed at the next available location within Block N at  104  and assuming the host next writes to a sector identified by the LBA  10 , the same is stored at  106 , followed by a host write to a sector identified by LBA  11 , which is written at  108 , LBA  50 , which is written at  110 , LBA  596 , written at  112  and LBA  597  at  114  and  598  at  116 . These are all shown to have been written to Block N. 
   In this example, the next time the host rewrites to or updates the sector identified by LBA  0 , this information is stored in Block N+M, at its first sector location,  116  and at such time, the information at  102  in Block N is designated as being ‘old’ through the use of a flag or other means while the sector information at  117  is designated as ‘new’. The same events occur when the scenario repeats itself for the updating of sector  1  where the location at  104  in Block N is designated as being ‘old’ and the location at  118  in Block N+M is designated as ‘new’ through the use of their respective flags. 
   The following sectors to be written, namely the sectors identified by LBAs  2 ,  3 ,  50 ,  496 ,  497  and  498 , are also stored in Block N+M at  120 – 130 , respectively. As shown, the sector identified by LBA  50  was previously written by the host and stored at  110  in Block N so that when it is updated, the new sector information is stored at  124  in Block N+M and the flag at  110  is modified to indicate ‘old’ whereas the flag at  124  is modified to indicate ‘new’. 
   In the example of  FIG. 2 , the following sector writes are of sectors of sequential LBA order. This sector information are stored in block N+M−1 at  132 – 146 , respectively. That is, the sector identified by LBA  400  is stored at  132 , the next sector, identified by LBA  402  is stored at  134  and so on until the eight sequential sectors are stored within the Block N+M−1. 
   At a time when all of the blocks  100  are filled with sector information or at the right time, the controller performs a ‘clean-up’ operation, arranging the sectors in sequential order within blocks other than those included with the blocks  100  thus enabling the space manager within the controller device to avoid maintaining track of information stored within nonvolatile memory on a sector-by-sector basis thereby improving manufacturing costs associated with the controller device by the latter having a smaller space manager requirement. Additionally, as will be evident, the number of move operations of sectors is reduced thereby increasing system performance. 
   Referring now to  FIG. 3 , free blocks are found by the controller and used for re-arranging sector information. In this example, as noted above, four blocks are employed while other number of blocks may be used without departing from the spirit and scope of the present invention. 
   In  FIG. 3 , blocks  200  are shown to include four blocks, namely Block  4 , Block  5 , Block  6  and Block  7 . Again, these blocks need not be Blocks  4 – 7  and can be any free blocks found by the controller. Each VLBA identifies a unique block having eight sectors. For example, VLBA 0  identifies Block  4 , VLBA  1  identified Block  6 , VLBA  2  identifies Block  5  and VLBA  6  identified Block  7 . It is important to note that the numbering of the VLBAs is a function of the sequential order of the LBAs associated with sectors. That is, sectors identified by LBA  0 – 7  will be located in VLBA 0  and the next eight sectors, LBA  8 – 15  will be in VLBA  1  and the next eight (not shown in  FIG. 3 ) will be in VLBA  2  and sectors identified by LBAs  496 ,  497 ,  498  through  503  are at VLBA  62  because 496 divided by 8 is 62, and sectors identified by LBAs  48  through  55  are at VLBA  6  and so on. 
   During ‘clean-up’, the sectors of  FIG. 2  having current sector information (not ‘old’ information) are re-arranged into sequential order and placed within the blocks  200  of  FIG. 3 . Starting with sector  0 , the sector identified by LBA  0 , is moved from  117  (in  FIG. 2) to 202  in  FIG. 3 . That is, the current sector  0  information, which now resides in Block N+M rather than Block N, is moved to the first location of Block  4 , at  202 . The sector that is in the next sequential order, i.e. sector  1 , is found in the blocks  100  of  FIG. 2 , at  118  and moved to  204  in  FIG. 3  (whenever reference is made throughout this document to moving a sector, the information within the sector or sector information is what is physically moved). Sector  2  is found at  120  in Block N+M in  FIG. 2  and moved to  206  in  FIG. 3  and sector  3  is found at  122  in  FIG. 2  and moved to  208  in  FIG. 3 . The next sequentially-ordered sector, sector  4  is found in Block  0  (shown in  FIG. 1(   b )) and moved to  210  in  FIG. 3  and the following 3 sectors follow at  212 ,  214  and  216  in  FIG. 3 . 
   The following eight sectors are sequentially placed within the block identified by VLBA  1  in  FIG. 3 . Each of these sectors is also found from various temporary block locations within blocks  100  in  FIG. 2  and moved to the locations  218 – 232 , respectively. That is, sectors  8  and  9  are found in Block  2  (shown in  FIG. 1(   b )) and moved to  218  and  220 , respectively. Sectors  10 – 11  are found at  104  and  106 , respectively in Block N of  FIG. 2  and remaining sectors  12 – 15  are found in Block  2  (shown in  FIG. 1(   b )) and placed at  226 – 232 , respectively. 
   In  FIG. 3 , VLBA  62  is shown to include information for sectors  496 – 503  with sectors  496 – 498  being moved from Block N+M at  124 – 130  of  FIG. 2 , respectively, to  250 – 254  of VLBA  62  of  FIG. 3 , respectively and sectors  499 – 503  being moved from Block  1 , not shown in  FIG. 2 , to  256 – 264  in  FIG. 3 , respectively. Without going through the details, in a similar fashion, VLBA  6  of  FIG. 3  is updated to include sectors  48 – 55  from temporary blocks  100 . 
   Referring back to  FIG. 2 , Block N+M−1 includes sectors that are already in sequential order, as noted above, since the host wrote them in sequential order. Accordingly, there is no need to move these sectors into another block for the purpose of reorganizing them into sequential order. Rather, Block N+M−1 is renumbered as VLBA Block  50  (this is due to sectors  400  as divided into 8 being 50) and taken out of temporary blocks  100  and considered among the blocks  200  of  FIG. 3 . Thus as shown in  FIG. 4 , no moves are required for sectors  400 – 408  saving a number of operations that substantially increases the system performance. In fact, the more the number of sequential writes of at least a number of sectors equal to the number of sectors within a block, the greater the system performance due to a lesser number of move operations. 
   Although the present invention has been described in terms of specific embodiments it is anticipated that alterations and modifications thereof will no doubt become apparent to those skilled in the art. It is therefore intended that the following claims be interpreted as covering all such alterations and modification as fall within the true spirit and scope of the invention.