Codeword management

Abstract

A method for managing an encoding process, the method includes receiving or determining, by a processor, (i) code rates for multiple pages, and (ii) sizes of a plurality of data segments to be stored in the multiple pages after being encoded to provide multiple codewords; determining, by the processor, sizes of the multiple codewords while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords, wherein a retrieval of the split data segment involves a retrieval of the at least two codewords; and sending to an encoder information about the sizes of the multiple codewords.

Description

BACKGROUND OF THE INVENTION

Flash memory devices such as NAND flash memory devices are built with rows of floating transistors. In single level cells (SLC) devices each transistor row is called page and can be programmed separately. SLC cells store a single bit of information per cell. In multiple level cells (MLC) devices each transistor holds several levels (multiple bits of information per cell), effectively each MLC flash row contains several pages. E.g. most significant bit (MSB) and Least significant bit (LSB) for 2 bit per cell flash devices, MSB, central significant bit (CSB) and LSB for 3 bit per cell.

A flash memory device, once programmed with data, may contain errors that may be present immediately or may be accumulated over the time. The amount of errors depends on many factors, including number of Program-Erase cycles page has undergone, time passed from programming moment, temperature and page physical properties.

In order to protect programmed data Error Correcting Codes (ECC) are used. Additionally to ECC other techniques may be used. E.g. DSP, data interleaving between several pages, etc.

Flash memory device rows may differ in their properties according to their physical location within flash memory block. In MLC flash devices different pages in a row (i.e. MSB, LSB) can have different properties too. There may be also difference in number of errors due to program coupling between pages, also called even and odd pages.

The reliability of a flash memory device depends on the reliability of all its components. The component with lowest reliability will define the reliability of entire system. In case on flash memory devices, pages with lowest reliability will define the reliability of entire system.

In order to get maximal reliability of the entire system, ECC code should fit page's quality. In a high quality page (i.e. less errors) a more relaxed ECC code can be used. In a lower quality page (i.e. more errors) a stronger ECC code can be used. Usually different ECC codes means different amount (or code rate) of code redundancy vs. payload data. Stronger code means more redundancy means lower code rate.

It is noted that the ECC may include applying a stronger ECC code than required. In such case lower code rate is got, more flash memory is used for redundancy, thus less capacity for user data. Such behavior is not optimal.

ECC code assignment with dependence on page reliability poses an implication Codeword size or Codeword Payload (AKA Payload) size changes from page to page. Such Code assignment technique can be called “Variable Code Rate”. This is in contrast, where all codes are equal, called “Fixed Code”.

Basic case of “Fixed Code” is “Nominal Code” which uses nominal amount of Bytes for user data and the rest for various Meta Data including ECC Meta Data. Nominal amount refers to the amount suggested by the specifications of the flash manufacturer.

A designer of system that includes a memory controller and a flash memory device may have several considerations in designing ECC codewords. Both reliability and performance considerations may be taken into account.

Once a code rate is set for a certain page it may contradict with other considerations such as a load imposed on the system in order to retrieve data segments as when a memory controller is requested to read a data segment (for example a 4 KB data segment), the memory controller must read all codewords that contain this data segment. I.e. round up to whole codewords. Even if only a small fraction of a data segment is contained by certain codeword. This causes transmission of more data over a link (or channel) between the flash memory device and the memory controller.

In some cases the amount of traffic may be twice the amount requested or even worse. This can cause performance degradation if the channel or ECC engine cannot support such traffic. It also causes power waste due to more channel and ECC engine operation.

FIG. 1 illustrates a prior art example of a relationship between codewords and data segments.

It is assumed that pages of the flash memory module are slightly longer than 16 KB and are designated to contain four data segments of 4 KB and codeword redundancies. Such configuration would be “Nominal Code”. 4 KB is the mostly used data unit due to computer operation systems' “page” based approach.

Once code rate is variable, pages with higher code rate contain more than 16 KB of user data, and pages with lower code rata contain less than 16 KB of data.

The first till twelfth codewords codeword_1—codeword_12 151-162 include redundancy 131-142 respectively.

First page (flash page) 101 is of a size of 16 KB+X, wherein X is the overall size of the redundancy of that page. The first page 101 stores first till fourth codewords codeword_1 codeword_4 151-154.

Each one of codeword_1-codeword_4 151-154 has a size of 4 KB+X/4. The first till fourth codewords includes first to fourth data segments (4 KB each) DS_1-DS_4 111-114 and redundancy 131-134.

The first till fourth codewords 151-154 are of a nominal code rate. The first till fourth data segments 111-114 are not split between codewords. Each one of these data segments can be retrieved by a single codeword transfer.

Second page (flash page) 102 is of a size of (16 KB+X), wherein X is the overall size of the redundancy of that page. The second page 102 includes fifth till eighth codewords codeword_5-codeword_8 155-158. These codewords include redundancy 135-138.

Each one of codeword_5-codeword_8 155-158 has a size of 4 KB+X/4, wherein the payload is 4.2 KB and the redundancy is X/4-0.2 KB.

Each one of codeword_5-codeword_8 155-158 includes portions of two data segments:

• • a. Codeword_5 155 includes portions of DS_5 115 and DS_6 116.
  • b. Codeword_6 156 includes portions of DS_6 116 and DS_7 117.
  • c. Codeword_7 158 includes portions of DS_7 117 and DS_8 118.
  • d. Codeword_8 155 includes portions of DS_8 118 and DS_9 119.

The fifth till eighth codewords 155-158 are of a higher than nominal code rate. The fifth till ninth data segments 115-119 are split between codewords.

Third page (flash page) 103 is of a size of 16 KB+X, wherein X is the overall size of the redundancy of that page. The third page includes ninth till twelfth codewords codeword_9-codeword_12 159-162. These codewords include redundancy 139-142.

Each one of codeword_9-codeword_12 159-162 has a size of 4 KB+X/4, wherein the payload is 3.8 KB and the redundancy is X/4+0.2 KB.

Each one of codeword_9-codeword_11 159-161 includes portions of two data segments:

• • a. Codeword_9 159 includes portions of DS_9 119 and DS_10 120.
  • b. Codeword_10 160 includes portions of DS_10 120 and DS_11 121.
  • c. Codeword_11 161 includes portions of DS_11 121 and DS_12 122.
    • Codeword_12 162 includes a portion of DS_12 122.

The ninth till twelfth codewords 159-162 are of a lower than nominal code rate. The ninth till twelfth data segments 119-122 are split between codewords. Each one of these data segments can be retrieved by a transferring pair of codewords.

SUMMARY

According to an embodiment of the invention there may be provided a method for managing an encoding process, the method may include receiving or determining, by a processor, (i) code rates for multiple pages, and (ii) sizes of a plurality of data segments to be stored in the multiple pages after being encoded to provide multiple codewords; determining, by the processor, sizes of the multiple codewords while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords wherein a retrieval of the split data segment involves a retrieval of the at least two codewords; and sending to an encoder information about the sizes of the multiple codewords.

The method may include receiving or determining, by the processor a flash memory transaction size; and wherein the determining of the sizes of the multiple codewords is further responsive to the flash memory transaction size.

The method may include determining the sizes of multiple codewords to minimize a number of codewords that may include at least a portion of two data segments.

The method may include determining the sizes of the multiple codewords so that at least one page of the multiple pages may include codewords that differ from each other by a size of redundancy.

The method may include determining the sizes of multiple codewords to allow only up to a single codeword per page to may include at least a portion of two data segments.

The code rates for the multiple pages may include a first code rate that is higher than a second code rate; wherein the first code rate is associated with a first page of the multiple pages and the second code rate is associated with a second page of the multiple pages.

The method may include preventing the second page from storing a codeword that may include at least a portion of two data segments.

The at least one codeword of the first page may include at least a portion of two data segments.

The method may include receiving the plurality of data segment and encoding the plurality of data segments to provide the multiple codewords, wherein the encoding is responsive to the information about the sizes of the multiple codewords.

According to an embodiment of the invention there may be provided a method for encoding data segments, the method may include receiving, by an encoder, information about sizes of multiple codewords to be generated by the encoder by encoding a plurality of codewords; wherein the sizes of the multiple codewords were determined (a) in response to code rates for multiple pages and sizes of the plurality of data segments, and (b) while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords, wherein a retrieval of the split data segment involves a retrieval of the at least two codewords; receiving, by the encoder, the plurality of data segment; and encoding, by the encoder, the plurality of data segments to provide the multiple codewords, wherein the encoding is responsive to the information about the sizes of the multiple codewords.

According to an embodiment of the invention there may be provided a non-transitory computer readable medium may store instructions that once executed by an encoder cause the encoder to execute the stages of receiving information about sizes of multiple codewords to be generated by the encoder by encoding a plurality of codewords; wherein the sizes of the multiple codewords were determined (a) in response to code rates for multiple pages and sizes of the plurality of data segments, and (b) while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords, wherein a retrieval of the split data segment involves a retrieval of the at least two codewords; receiving the plurality of data segment; and encoding the plurality of data segments to provide the multiple codewords, wherein the encoding is responsive to the information about the sizes of the multiple codewords.

The non-transitory computer readable medium may store instructions for receiving or determining, by the processor a flash memory transaction size; and wherein the determining of the sizes of the multiple codewords is further responsive to the flash memory transaction size.

The non-transitory computer readable medium may store instructions for determining the sizes of multiple codewords to minimize a number of codewords that may include at least a portion of two data segments.

The non-transitory computer readable medium may store instructions for determining the sizes of the multiple codewords so that at least one page of the multiple pages may include codewords that differ from each other by a size of redundancy.

The non-transitory computer readable medium may store instructions for determining the sizes of multiple codewords to allow only up to a single codeword per page to may include at least a portion of two data segments.

The code rates for the multiple pages may include a first code rate that is higher than a second code rate; wherein the first code rate is associated with a first page of the multiple pages and the second code rate is associated with a second page of the multiple pages.

The non-transitory computer readable medium may store instructions for preventing the second page from storing a codeword that may include at least a portion of two data segments.

At least one codeword of the first page may include at least a portion of two data segments.

The non-transitory computer readable medium may store instructions for receiving the plurality of data segment and encoding the plurality of data segments to provide the multiple codewords, wherein the encoding is responsive to the information about the sizes of the multiple codewords.

According to an embodiment of the invention there may be provided a non-transitory computer readable medium may store instructions that once executed by a processor cause the processor to execute the stage of receiving or determining (i) code rates for multiple pages, and (ii) sizes of a plurality of data segments to be stored in the multiple pages after being encoded to provide multiple codewords; determining sizes of the multiple codewords while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords, wherein a retrieval of the split data segment involves a retrieval of the at least two codewords; and sending to an encoder information about the sizes of the multiple codewords.

According to an embodiment of the invention there may be provided a memory controller that may include an encoder; wherein the encoder is configured to receive information about sizes of multiple codewords to be generated by the encoder by encoding a plurality of codewords; wherein the sizes of the multiple codewords were determined (a) in response to code rates for multiple pages and sizes of the plurality of data segments, and (b) while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords, wherein a retrieval of the split data segment involves a retrieval of the at least two codewords; receive the plurality of data segment; and encode the plurality of data segments to provide the multiple codewords, wherein the encoding is responsive to the information about the sizes of the multiple codewords.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings in which:

FIG. 1 illustrates a prior art example of a relationship between codewords and data segments;

FIG. 2 illustrates a method for managing an encoding process, according to an embodiment of the invention;

FIG. 3 illustrates an allocation of codewords and data segments according to an embodiment of the invention;

FIG. 4 illustrates a method for encoding data segments, according to an embodiment of the invention; and

FIG. 5 illustrates a device and a user computer according to an embodiment of the invention.

DETAILED DESCRIPTION OF THE DRAWINGS

In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the present invention.

The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings.

It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.

Because the illustrated embodiments of the present invention may for the most part, be implemented using electronic components and circuits known to those skilled in the art, details will not be explained in any greater extent than that considered necessary as illustrated above, for the understanding and appreciation of the underlying concepts of the present invention and in order not to obfuscate or distract from the teachings of the present invention.

Any reference in the specification to a method should be applied mutatis mutandis to a system capable of executing the method and should be applied mutatis mutandis to a non-transitory computer readable medium that stores instructions that once executed by a computer result in the execution of the method.

Any reference in the specification to a system should be applied mutatis mutandis to a method that may be executed by the system and should be applied mutatis mutandis to a non-transitory computer readable medium that stores instructions that may be executed by the system.

Any reference in the specification to a non-transitory computer readable medium should be applied mutatis mutandis to a system capable of executing the instructions stored in the non-transitory computer readable medium and should be applied mutatis mutandis to method that may be executed by a computer that reads the instructions stored in the non-transitory computer readable medium.

FIG. 2 illustrates method 300 for managing an encoding process, according to an embodiment of the invention.

Method 300 may start by stage 310 of receiving or determining, by a processor, (i) code rates for multiple pages, and (ii) sizes of a plurality of data segments to be stored in the multiple pages after being encoded to provide multiple codewords.

Stage 310 may be followed by stage 320 of determining, by the processor, sizes of the multiple codewords while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords, wherein a retrieval of the split data segment involves a retrieval of the at least two codewords. This retrieval may require one or multiple flash memory transactions.

Stage 310 may include receiving a flash memory transaction size and stage 320 of determining may also be responsive to the flash memory transaction size.

Stage 320 may include at least one out of:

• • a. Stage 321 of determining the sizes of multiple codewords to minimize a number of codewords that comprise at least a portion of two data segments. Additionally or alternatively, stage 321 may include having a maximal number of data segments wherein each data segment is fully included in a single codeword.
  • b. Stage 322 of determining the sizes of the multiple codewords so that at least one page of the multiple pages comprises codewords that differ from each other by a size of redundancy.
  • c. Stage 323 of determining the sizes of multiple codewords to allow only up to a single codeword per page to comprise at least a portion of two data segments.
  • d. Stage 324 of preventing a second page from storing a codeword that comprises at least a portion of two data segments. It is noted that the code rates for the multiple pages may include a first code rate that is higher than a second code rate; wherein the first code rate is associated with a first page of the multiple pages and the second code rate is associated with a second page of the multiple pages.
  • e. Stage 325 of determining the sizes of the multiple codewords so that at least one codeword of the first page comprises at least a portion of two data segments.

Stage 320 may be followed by stage 330 of responding to the determination.

Stage 330 may include at least one out of:

• • a. Stage 331 of storing the information about the sizes of the multiple codewords.
  • b. Stage 332 of sending to an encoder information about the sizes of the multiple codewords. The encoder may be included in a memory controller. The sending to the encoder may include sending the information directly to the encoder or sending the information such that eventually the information may be provided to the encoder.
  • c. Stage 333 of receiving the plurality of data segments and encoding the plurality of data segments to provide the multiple codewords, wherein the encoding is responsive to the information about the sizes of the multiple codewords.
  • d. Stage 334 of informing a user about the sizes of the multiple codewords.

FIG. 3 illustrates an allocation of codewords and data segments according to an embodiment of the invention.

First page (flash page) 201 is of a size of (16 KB+X), wherein X is the overall size of the redundancy of that page. First page 201 includes first till fourth codewords denoted codeword #1-codeword #4 251-254.

Each one of codeword #1-codeword #4 251-254 has a size of 4 KB+X/4. These codewords include first to fourth data segments (4 KB each) DS_1-DS_4 111-114 and redundancy 231-234.

The first till fourth codewords 251-254 are of a nominal code rate. The first till fourth data segments 111-114 are not split between codewords. Each one of these data segments can be retrieved by a single transfer.

Second page (flash page) 202 is of a size of (16 KB+X), wherein Xis the overall size of the redundancy of that page. Second page 202 includes fifth till ninth codewords codeword #5-codeword #8 255-258. These codewords include redundancy 235-238.

Each one of codeword #5-codeword #7 255-257 has a size of 4 KB+(X/4−0.2 KB)*4/4.2, wherein the payload is 4 KB and the redundancy is (X/4-0.2 KB)*4/4.2.

Each one of codeword #5-codeword #7 255-257 includes a single data segment−fifth till seventh codewords (codeword #5-codeword #7 255-258) include first to seventh data segments DS_5-DS_7 115-117.

The eighth codeword (codeword #8 258) includes the entire eighth data segment DS_8 118 and a first portion of the ninth data segment DS_9 119.

The fifth till eighth codewords 255-258 are of a higher than nominal code rate. Only the ninth data segment 119 is split between codewords.

Third page (flash page) 203 is of a size of (16 KB+X), wherein X is the overall size of the redundancy of that page. The third page includes the ninth till twelfth codewords —codeword #9-#12 259-262. These codewords include redundancy 239-242.

Each one of codeword #10-codeword #12 260-262 has a size of 4 KB+(X/4+0.2 KB)*4/3.8. The payload is 4 KB and the redundancy is (X/4+0.2 KB)*4/3.8.

The size of the ninth codeword (codeword #9) is payload 3.2 KB and redundancy (X/4+0.2 KB)*3.2/3.8.

Each one of codeword #10-codeword #12 260-262 includes a single data segment.

The eighth till twelfth codewords 259-262 are of a lower than nominal code rate. Only the ninth data segment 119 is split between codewords and also split between pages. Each one of the tenth till twelfth data segments can be retrieved by a single transfer.

FIG. 4 illustrates method 400 for encoding data segments, according to an embodiment of the invention.

Method 400 may use information about a size of multiple codewords that were determined by method 300.

Method 400 may start by stage 410 of receiving, by an encoder, information about sizes of multiple codewords to be generated by the encoder by encoding a plurality of codewords; wherein the sizes of the multiple codewords were determined (a) in response to code rates for multiple pages, and sizes of the plurality of data segments, and (b) while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords, wherein a retrieval of the split data segment involves a retrieval of the at least two codewords. This may involve multiple flash memory transactions. The sizes may have been determined also in response to a flash memory transaction size.

Stage 410 may be followed by stage 420 of receiving, by the encoder, the plurality of data segment.

Stage 420 may be followed by stage 430 of encoding, by the encoder, the plurality of data segments to provide the multiple codewords, wherein the encoding is responsive to the information about the sizes of the multiple codewords.

Stage 430 may be followed by stage 440 of storing the multiple codewords in the multiple pages (of a flash memory module).

FIG. 5 illustrates a device 70 and a user computer 10 according to an embodiment of the invention.

User computer 10 may be a laptop, desktop, server or any type of computer. It may include components such as a processor and a memory module 16. The user computer may allow a user to execute the stages of method 300.

Device 70 may be a computerized device that may include a host computer 40 (that may be any type of a processor), a memory controller 20 and a flash memory module 30. Channel (link) 50 couples the memory controller 20 to the host computer 40 and channel 60 coupled the memory controller 20 to the flash memory module 30. Transactions over at least one of these channels may be limited by the flash memory transaction size.

Memory controller 20 can execute the stages of method 300 and/or the stages of method 400.

The memory controller 20 is illustrated as including an encoder 21 (for encoding), a processor 22 (general purpose processor and/or dedicated processor that may execute software/firmware/middleware), a write circuit 23, a read circuit 24 and an erase circuit 25 for writing data to the flash memory module, reading data from the flash memory module and for erasing erase blocks of the flash memory module respectively.

The flash memory module 30 may include multiple erase blocks (such as first till R'th erase blocks 31(1)-31(R), R being a positive integer. Each erase block has multiple pages such as first till S'th pages of first erase block 31(1,1)-31(S,1), S being a positive integer.

Performance Impact

Variables: π—Page size; ξ—CW size (≈4 KB); NBW—channel BW

Prior art “configuration for performance”

Scenarios “Best Case”: 4 KB alignment is restored each 2 pages and codeword sizes: ξ0=4 KB-ε, ξ1=4 KB+ε

“Worst case”: 4 KB has negligible probability to be aligned to page or Code Word.

Calculations: Probability of 4 KB data to cross page boundaries: Best case:

$P_{\mathrm{Cross}}=\frac{4KB}{2\pi },\mathrm{Worst}\mathrm{case}\text{:}{P}_{\mathrm{Cross}}=\frac{4KB}{\pi }.$

Probability of 4 KB data to be contained within single ˜4 KB codeword Best case:

$P_{\mathrm{Contain}}=\frac{4KB}{2\pi }.$

Because only the segment that resides in page with 41 and is aligned to page boundary will be fully included in CW.

Worst case: Probability is negligible P_contain≅0.

Random Read performance [IOPS]:

$1/\left(\mathrm{tR}·\left(1+P_{\mathrm{Cross}}\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}·\left(2-P_{\mathrm{Contain}}\right)\right).$

Best Case:

$1/\left(\mathrm{tR}·\left(1+\frac{4\mathrm{KB}}{2\pi }\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}·\left(2-\frac{4\mathrm{KB}}{2\pi }\right)\right)=\pi /\left(\mathrm{tR}·\left(\pi +2\mathrm{KB}\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}·\left(2\pi -2\mathrm{KB}\right)\right)$

Worst Case:

$1/\left(\mathrm{tR}·\left(1+\frac{4\mathrm{KB}}{\pi }\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}·\left(2-0\right)\right)=\pi /\left(\mathrm{tR}·\left(\pi +4\mathrm{KB}\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}·2\pi \right)$

Random Read channel load [IOPS]:

$\frac{\mathrm{NBW}}{4\mathrm{KB}·\left(2-P_{\mathrm{Contain}}\right)}$

Best Case:

$\frac{\mathrm{NBW}}{4\mathrm{KB}·\left(2-\frac{4\mathrm{KB}}{2\pi }\right)}=\frac{\mathrm{NBW}·\pi }{4\mathrm{KB}·\left(2\pi -2\mathrm{KB}\right)}$

Worst Case:

$\frac{\mathrm{NBW}}{4\mathrm{KB}·\left(2-0\right)}=\frac{\mathrm{NBW}}{8\mathrm{KB}}$

In short, the channel load is approximately twice that of a system that uses constant 4 KB codes (no variable coding). This leads to twice the channel bandwidth requirements, power requirements, etc.

Suggested “configuration for performance

The suggested configuration decreases the impact of lack of alignment between codeword and 4 KB data segment.

Most codewords are aligned to data. I.e. most codewords contain exactly 4 KB payload data, which is aligned to logical address. Only a small fraction of codewords contain different amount of data. Later codewords used to handle page boundaries. Those codewords are minority and thus low performance impact.

Some data segments are not fully included within the page, i.e. they cross page boundary. This occurs on page start or end. Those cases get special treatment.

Two options may be used: (1) partial chunk enclosure within smaller codeword, (2) concatenate partial chunk with nearby full 4 KB data segment and enclose within larger codeword. Consideration which policy to use may come from reliability consideration: larger codeword usually better reliability. On other hand ECC engine capabilities may limit the maximal codeword size.

Probability of 4 KB data to cross page boundaries stays the same.

Probability of 4 KB data to be contained within single ˜4 KB codeword is improved significantly: Best case:

$P_{\mathrm{Contain}}=1-\frac{4\mathrm{KB}}{2\pi }.$

Because only the segment that crosses pages is divided between 2 codewords.

Worst case:

$P_{\mathrm{Contain}}\cong 1-\frac{4\mathrm{KB}}{\pi }$ all boundary 4 KB segments are divided

Random Read performance [IOPS]: Best Case:

$1/\left(\mathrm{tR}·\left(1+\frac{4\mathrm{KB}}{2\pi }\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}·\left(2-\left(1-\frac{4\mathrm{KB}}{2\pi }\right)\right)\right)=\pi /\left(\mathrm{tR}·\left(\pi +2\mathrm{KB}\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}·\left(\pi +2\mathrm{KB}\right)\right)$

Worst Case

$1/\left(\mathrm{tR}·\left(1+\frac{4\mathrm{KB}}{\pi }\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}·\left(2-\left(1-\frac{4\mathrm{KB}}{\pi }\right)\right)\right)=\pi /\left(\mathrm{tR}·\left(\pi +4\mathrm{KB}\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}·\left(\pi -4\mathrm{KB}\right)\right)$

Random Read channel load [IOPS] Best Case:

$\frac{\mathrm{NBW}}{4\mathrm{KB}·\left(2-\left(1-\frac{4\mathrm{KB}}{2\pi }\right)\right)}=\frac{\mathrm{NBW}·\pi }{4\mathrm{KB}·\left(\pi +2\mathrm{KB}\right)},$ Worst Case:

$\frac{\mathrm{NBW}}{4\mathrm{KB}·\left(2-\left(1-\frac{4\mathrm{KB}}{\pi }\right)\right)}=\frac{\mathrm{NBW}·\pi }{4\mathrm{KB}·\left(\pi +4\mathrm{KB}\right)}$

In short, the channel load is now much closer to that of a system that uses constant 4 KB codes (no variable coding). Thus allowing saving in channel bandwidth requirements, power requirements and still keep higher reliability compared to a system with aligned and constant 4 KB code sizes.

Improvement in pure Random Read performance [IOPS] Best Case:

$\frac{\pi /\left(\mathrm{tR}\left(\pi +2\mathrm{KB}\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}\left(\pi +2\mathrm{KB}\right)\right)}{\pi /\left(\mathrm{tR}\left(\pi +2\mathrm{KB}\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}\left(2\pi -2\mathrm{KB}\right)\right)}\stackrel{\pi ⪢4\mathrm{KB},\mathrm{tR}⪢\frac{4\mathrm{KB}}{\mathrm{NBW}}}{\to }\approx \frac{\left(\mathrm{tR}+\frac{8\mathrm{KB}}{\mathrm{NBW}}\right)}{\left(\mathrm{tR}+\frac{4\mathrm{KB}}{\mathrm{NBW}}\right)}\approx 1$

Worst Case:

$\frac{\pi /\left(\mathrm{tR}\left(\pi +4\mathrm{KB}\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}·\left(\pi -4\mathrm{KB}\right)\right)}{\pi /\left(\mathrm{tR}\left(\pi +4\mathrm{KB}\right)+\frac{4\mathrm{KB}}{\mathrm{NBW}}·2\pi \right)}\stackrel{\pi ⪢4\mathrm{KB},\mathrm{tR}⪢\frac{4\mathrm{KB}}{\mathrm{NBW}}}{\to }\approx \frac{\left(\mathrm{tR}+\frac{8\mathrm{KB}}{\mathrm{NBW}}\right)}{\left(\mathrm{tR}+\frac{4\mathrm{KB}}{\mathrm{NBW}}\right)}\approx 1$

Improvement in channel load [IOPS]

Best Case:

$\frac{\frac{\mathrm{NBW}·\pi }{4\mathrm{KB}·\left(\pi +2\mathrm{KB}\right)}}{\frac{\mathrm{NBW}·\pi }{4\mathrm{KB}·\left(2\pi -2\mathrm{KB}\right)}}=\frac{\left(2\pi -2\mathrm{KB}\right)}{\left(\pi +2\mathrm{KB}\right)}\stackrel{\pi ⪢2\mathrm{KB}}{\to }\approx 2.$

Worst Case:

$\frac{\frac{\mathrm{NBW}·\pi }{4\mathrm{KB}·\left(\pi +4\mathrm{KB}\right)}}{\frac{\mathrm{NBW}}{8\mathrm{KB}}}=\frac{2\pi }{\left(\pi +4\mathrm{KB}\right)}\stackrel{\pi ⪢4\mathrm{KB}}{\to }\approx 2$

Accordingly, assuming a page size is significantly larger than 4 KB (i.e. π>>4 KB). E.g. page of 16 or 32 KB, channel BW is high enough, so 4 KB transfer time is significantly lower than tR

$\left(tR⪢\frac{4KB}{NBW}\right).$ E.g.

$\left(\mathrm{tR}=50\mathrm{us}\right)⪢\left(\frac{4\mathrm{KB}}{\mathrm{NBW}=\frac{200\mathrm{MB}}{s}}=20\mathrm{us}\right)$

Pure Random Read performance seems not affected significantly.

The invention may also be implemented in a computer program for running on a computer system, at least including code portions for performing steps of a method according to the invention when run on a programmable apparatus, such as a computer system or enabling a programmable apparatus to perform functions of a device or system according to the invention. The computer program may cause the storage system to allocate disk drives to disk drive groups.

A computer program is a list of instructions such as a particular application program and/or an operating system. The computer program may for instance include one or more of a subroutine, a function, a procedure, an object method, an object implementation, an executable application, an applet, a servlet, a source code, an object code, a shared library/dynamic load library and/or other sequence of instructions designed for execution on a computer system.

The computer program may be stored internally on a non-transitory computer readable medium. All or some of the computer program may be provided on computer readable media permanently, removably or remotely coupled to an information processing system. The computer readable media may include, for example and without limitation, any number of the following magnetic storage media including disk and tape storage media; optical storage media such as compact disk media (e.g., CD-ROM, CD-R, etc.) and digital video disk storage media; nonvolatile memory storage media including semiconductor-based memory units such as flash memory, EEPROM, EPROM, ROM; ferromagnetic digital memories; MRAM; volatile storage media including registers, buffers or caches, main memory, RAM, etc.

A computer process typically includes an executing (running) program or portion of a program, current program values and state information, and the resources used by the operating system to manage the execution of the process. An operating system (OS) is the software that manages the sharing of the resources of a computer and provides programmers with an interface used to access those resources. An operating system processes system data and user input, and responds by allocating and managing tasks and internal system resources as a service to users and programs of the system.

The computer system may for instance include at least one processing unit, associated memory and a number of input/output (I/O) devices. When executing the computer program, the computer system processes information according to the computer program and produces resultant output information via I/O devices.

In the foregoing specification, the invention has been described with reference to specific examples of embodiments of the invention. It will, however, be evident that various modifications and changes may be made therein without departing from the broader spirit and scope of the invention as set forth in the appended claims.

Moreover, the terms “front,” “back,” “top,” “bottom,” “over,” “under” and the like in the description and in the claims, if any, are used for descriptive purposes and not necessarily for describing permanent relative positions. It is understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in other orientations than those illustrated or otherwise described herein.

The connections as discussed herein may be any type of connection suitable to transfer signals from or to the respective nodes, units or devices, for example via intermediate devices. Accordingly, unless implied or stated otherwise, the connections may for example be direct connections or indirect connections. The connections may be illustrated or described in reference to being a single connection, a plurality of connections, unidirectional connections, or bidirectional connections. However, different embodiments may vary the implementation of the connections. For example, separate unidirectional connections may be used rather than bidirectional connections and vice versa. Also, plurality of connections may be replaced with a single connection that transfers multiple signals serially or in a time multiplexed manner. Likewise, single connections carrying multiple signals may be separated out into various different connections carrying subsets of these signals. Therefore, many options exist for transferring signals.

Although specific conductivity types or polarity of potentials have been described in the examples, it will be appreciated that conductivity types and polarities of potentials may be reversed.

Each signal described herein may be designed as positive or negative logic. In the case of a negative logic signal, the signal is active low where the logically true state corresponds to a logic level zero. In the case of a positive logic signal, the signal is active high where the logically true state corresponds to a logic level one. Note that any of the signals described herein may be designed as either negative or positive logic signals. Therefore, in alternate embodiments, those signals described as positive logic signals may be implemented as negative logic signals, and those signals described as negative logic signals may be implemented as positive logic signals.

Furthermore, the terms “assert” or “set” and “negate” (or “deassert” or “clear”) are used herein when referring to the rendering of a signal, status bit, or similar apparatus into its logically true or logically false state, respectively. If the logically true state is a logic level one, the logically false state is a logic level zero. And if the logically true state is a logic level zero, the logically false state is a logic level one.

Those skilled in the art will recognize that the boundaries between logic blocks are merely illustrative and that alternative embodiments may merge logic blocks or circuit elements or impose an alternate decomposition of functionality upon various logic blocks or circuit elements. Thus, it is to be understood that the architectures depicted herein are merely exemplary, and that in fact many other architectures may be implemented which achieve the same functionality.

Any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected,” or “operably coupled,” to each other to achieve the desired functionality.

Furthermore, those skilled in the art will recognize that boundaries between the above described operations merely illustrative. The multiple operations may be combined into a single operation, a single operation may be distributed in additional operations and operations may be executed at least partially overlapping in time. Moreover, alternative embodiments may include multiple instances of a particular operation, and the order of operations may be altered in various other embodiments.

Also for example, in one embodiment, the illustrated examples may be implemented as circuitry located on a single integrated circuit or within a same device. Alternatively, the examples may be implemented as any number of separate integrated circuits or separate devices interconnected with each other in a suitable manner.

Also for example, the examples, or portions thereof, may implemented as soft or code representations of physical circuitry or of logical representations convertible into physical circuitry, such as in a hardware description language of any appropriate type.

Also, the invention is not limited to physical devices or units implemented in non-programmable hardware but can also be applied in programmable devices or units able to perform the desired device functions by operating in accordance with suitable program code, such as mainframes, minicomputers, servers, workstations, personal computers, notepads, personal digital assistants, electronic games, automotive and other embedded systems, cell phones and various other wireless devices, commonly denoted in this application as ‘computer systems’.

However, other modifications, variations and alternatives are also possible. The specifications and drawings are, accordingly, to be regarded in an illustrative rather than in a restrictive sense.

In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word ‘comprising’ does not exclude the presence of other elements or steps then those listed in a claim. Furthermore, the terms “a” or “an,” as used herein, are defined as one or more than one. Also, the use of introductory phrases such as “at least one” and “one or more” in the claims should not be construed to imply that the introduction of another claim element by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim element to inventions containing only one such element, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an.” The same holds true for the use of definite articles. Unless stated otherwise, terms such as “first” and “second” are used to arbitrarily distinguish between the elements such terms describe. Thus, these terms are not necessarily intended to indicate temporal or other prioritization of such elements. The mere fact that certain measures are recited in mutually different claims does not indicate that a combination of these measures cannot be used to advantage.

While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents will now occur to those of ordinary skill in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.

Claims

1. A method for managing an encoding process, the method comprises: receiving or determining, by a processor, (i) code rates for multiple pages of a flash memory, and (ii) sizes of a plurality of data segments to be stored in the multiple pages after being encoded to provide multiple codewords;determining, by the processor, sizes of the multiple codewords while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords, wherein a retrieval, from the flash memory, of each split data segment that is stored in the flash memory and is split between the at least two codewords involves a retrieval of the at least two codewords; andsending to an encoder information about the sizes of the multiple codewords.

2. The method according to claim 1 further comprising receiving or determining, by the processor a flash memory transaction size; and wherein the determining of the sizes of the multiple codewords is further responsive to the flash memory transaction size.

3. The method according to claim 1, comprising determining the sizes of multiple codewords to minimize a number of codewords that comprise at least a portion of two data segments.

4. The method according to claim 1, comprising determining the sizes of the multiple codewords so that at least one page of the multiple pages comprises codewords that differ from each other by a size of redundancy.

5. The method according to claim 1, comprising determining the sizes of multiple codewords to allow only up to a single codeword per page to comprise at least a portion of two data segments.

6. The method according to claim 1, wherein the code rates for the multiple pages comprise a first code rate that is higher than a second code rate; wherein the first code rate is associated with a first page of the multiple pages and the second code rate is associated with a second page of the multiple pages.

7. The method according to claim 6 comprising preventing the second page from storing a codeword that comprises at least a portion of two data segments.

8. The method according to claim 6 wherein at least one codeword of the first page comprises at least a portion of two data segments.

9. The method according to claim 1 further comprising receiving the plurality of data segment and encoding the plurality of data segments to provide the multiple codewords, wherein the encoding is responsive to the information about the sizes of the multiple codewords.

10. A method for encoding data segments, the method comprises: receiving, by an encoder, information about sizes of multiple codewords to be generated by the encoder by encoding a plurality of codewords; wherein the sizes of the multiple codewords were determined (a) in response to code rates for multiple pages of a flash memory and sizes of the plurality of data segments, and (b) while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords, wherein a retrieval, from the flash memory, of each split data segment that is stored in the flash memory and is split between the at least two codewords involves a retrieval of the at least two codewords;receiving, by the encoder, the plurality of data segment; andencoding, by the encoder, the plurality of data segments to provide the multiple codewords, wherein the encoding is responsive to the information about the sizes of the multiple codewords.

11. A non-transitory computer readable medium that stores instructions that once executed by an encoder cause the encoder to execute the stages of: receiving information about sizes of multiple codewords to be generated by the encoder by encoding a plurality of codewords; wherein the sizes of the multiple codewords were determined (a) in response to code rates for multiple pages of a flash memory and sizes of the plurality of data segments, and (b) while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords, wherein a retrieval, from the flash memory, of each split data segment that is stored in the flash memory and is split between the at least two codewords involves a retrieval of the at least two codewords; receiving the plurality of data segment; and encoding the plurality of data segments to provide the multiple codewords, wherein the encoding is responsive to the information about the sizes of the multiple codewords.

12. The non-transitory computer readable medium according to claim 11 that stores instructions for receiving or determining, by the processor a flash memory transaction size; and wherein the determining of the sizes of the multiple codewords is further responsive to the flash memory transaction size.

13. The non-transitory computer readable medium according to claim 11, that stores instructions for determining the sizes of multiple codewords to minimize a number of codewords that comprise at least a portion of two data segments.

14. The non-transitory computer readable medium according to claim 11, that stores instructions for determining the sizes of the multiple codewords so that at least one page of the multiple pages comprises codewords that differ from each other by a size of redundancy.

15. The non-transitory computer readable medium according to claim 11, that stores instructions for determining the sizes of multiple codewords to allow only up to a single codeword per page to comprise at least a portion of two data segments.

16. The non-transitory computer readable medium according to claim 11, wherein the code rates for the multiple pages comprise a first code rate that is higher than a second code rate; wherein the first code rate is associated with a first page of the multiple pages and the second code rate is associated with a second page of the multiple pages.

17. The non-transitory computer readable medium according to claim 16 that stores instructions for preventing the second page from storing a codeword that comprises at least a portion of two data segments.

18. The non-transitory computer readable medium according to claim 16 wherein at least one codeword of the first page comprises at least a portion of two data segments.

19. The non-transitory computer readable medium according to claim 11 that stores instructions for receiving the plurality of data segment and encoding the plurality of data segments to provide the multiple codewords, wherein the encoding is responsive to the information about the sizes of the multiple codewords.

20. A non-transitory computer readable medium that stores instructions that once executed by a processor cause the processor to execute the stage of receiving or determining (i) code rates for multiple pages of a flash memory, and (ii) sizes of a plurality of data segments to be stored in the multiple pages after being encoded to provide multiple codewords; determining sizes of the multiple codewords while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords, wherein a retrieval, from the flash memory, of each split data segment that is stored in the flash memory and is split between the at least two codewords involves a retrieval of the at least two codewords; and sending to an encoder information about the sizes of the multiple codewords.

21. A memory controller that comprises an encoder; wherein the encoder is configured to: receive information about sizes of multiple codewords to be generated by the encoder by encoding a plurality of codewords; wherein the sizes of the multiple codewords were determined (a) in response to code rates for multiple pages of a flash memory and sizes of the plurality of data segments, and (b) while maintaining the code rates for the multiple pages and minimizing a number of split data segments out of the plurality of data segments, wherein each split data segment is split between at least two codewords of the multiple codewords, wherein a retrieval, from the flash memory, of each split data segment that is stored in the flash memory and is split between the at least two codewords involves a retrieval of the at least two codewords; receive the plurality of data segment; andencode the plurality of data segments to provide the multiple codewords, wherein the encoding is responsive to the information about the sizes of the multiple codewords.