From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: jens.axboe@oracle.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: [PATCH 0 of 3] Block Layer Data Integrity
Date: Tue, 17 Jun 2008 11:57:55 -0400 [thread overview]
Message-ID: <patchbomb.1213718275@sermon.lab.mkp.net> (raw)
These patches allow data integrity information (checksum and more) to
be attached to I/Os at the block/filesystem layers and transferred
through the entire I/O stack all the way to the physical storage
device.
The integrity metadata can be generated in close proximity to the
original data. Capable host adapters, RAID arrays and physical disks
can verify the data integrity and abort I/Os in case of a mismatch.
Changes:
- Add "if in doubt" to Kconfig
- Make blk_rq_count_integrity_sg() more readable
- Queue integrity sysfs fixes
- Fix two struct bi leaks
- Rename struct bip to bio_integrity_payload
- Introduce bio_integrity_hw_sectors() that converts from block layer
(512b) sectors to hardware sectors
- Fix kunmap_atomic() abuse
- Replace ?: constructs with if()
- Add __GFP_NOFAIL to bio_integrity_prep() allocation
next reply other threads:[~2008-06-17 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 15:57 Martin K. Petersen [this message]
2008-06-17 15:57 ` [PATCH 1 of 3] block: Globalize bio_set and bio_vec_slab Martin K. Petersen
2008-06-17 15:57 ` [PATCH 2 of 3] block: Block layer data integrity support Martin K. Petersen
2008-06-17 15:57 ` [PATCH 3 of 3] block: Data integrity infrastructure documentation Martin K. Petersen
2008-06-17 16:57 ` [PATCH 0 of 3] Block Layer Data Integrity Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2008-06-16 4:10 Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=patchbomb.1213718275@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox