diff options
| author | Ingo Molnar <mingo@elte.hu> | 2009-08-15 12:55:58 -0400 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2009-08-15 12:56:13 -0400 |
| commit | fa08661af834875c9bd6f7f0b1b9388dc72a6585 (patch) | |
| tree | c381fcfcfeb38515bfa93445c80ad9231343414d /Documentation/block/data-integrity.txt | |
| parent | 240ebbf81f149b11a31e060ebe5ee51a3c775360 (diff) | |
| parent | 64f1607ffbbc772685733ea63e6f7f4183df1b16 (diff) | |
Merge commit 'v2.6.31-rc6' into core/rcu
Merge reason: the branch was on pre-rc1 .30, update to latest.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'Documentation/block/data-integrity.txt')
| -rw-r--r-- | Documentation/block/data-integrity.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/block/data-integrity.txt b/Documentation/block/data-integrity.txt index e8ca040ba2cf..2d735b0ae383 100644 --- a/Documentation/block/data-integrity.txt +++ b/Documentation/block/data-integrity.txt | |||
| @@ -50,7 +50,7 @@ encouraged them to allow separation of the data and integrity metadata | |||
| 50 | scatter-gather lists. | 50 | scatter-gather lists. |
| 51 | 51 | ||
| 52 | The controller will interleave the buffers on write and split them on | 52 | The controller will interleave the buffers on write and split them on |
| 53 | read. This means that the Linux can DMA the data buffers to and from | 53 | read. This means that Linux can DMA the data buffers to and from |
| 54 | host memory without changes to the page cache. | 54 | host memory without changes to the page cache. |
| 55 | 55 | ||
| 56 | Also, the 16-bit CRC checksum mandated by both the SCSI and SATA specs | 56 | Also, the 16-bit CRC checksum mandated by both the SCSI and SATA specs |
| @@ -66,7 +66,7 @@ software RAID5). | |||
| 66 | 66 | ||
| 67 | The IP checksum is weaker than the CRC in terms of detecting bit | 67 | The IP checksum is weaker than the CRC in terms of detecting bit |
| 68 | errors. However, the strength is really in the separation of the data | 68 | errors. However, the strength is really in the separation of the data |
| 69 | buffers and the integrity metadata. These two distinct buffers much | 69 | buffers and the integrity metadata. These two distinct buffers must |
| 70 | match up for an I/O to complete. | 70 | match up for an I/O to complete. |
| 71 | 71 | ||
| 72 | The separation of the data and integrity metadata buffers as well as | 72 | The separation of the data and integrity metadata buffers as well as |