From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James.Bottomley@HansenPartnership.com, linux-scsi@vger.kernel.org
Subject: [PATCH 0 of 6] SCSI Data Integrity Support
Date: Wed, 09 Jul 2008 22:48:02 -0400 [thread overview]
Message-ID: <patchbomb.1215658082@sermon.lab.mkp.net> (raw)
Another post of my SCSI DIF changes. These patches require the block
layer integrity infrastructure in Jens' tree as well as the patches
that James took already.
The complete patch series against 2.6.26rc9 is available here:
http://oss.oracle.com/~mkp/patches/
Changes since last post:
- Make the distinction between DIF and DIX clearer in the scsi_host
settings.
- Revamp DIF/DIX negotiation to support all combinations.
- Error handling: Correctly handle failures detected by HBA and disk
respectively.
- Integrate protection scsi_data_buffer allocation with the command
pools.
- scsi_device_protection() accessor.
- Remove unnecessary printks at disk init time.
--
Martin K. Petersen Oracle Linux Engineering
next reply other threads:[~2008-07-10 2:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 2:48 Martin K. Petersen [this message]
2008-07-10 2:48 ` [PATCH 1 of 6] scsi: Host protection capabilities Martin K. Petersen
2008-07-10 2:48 ` [PATCH 2 of 6] scsi: Command protection operation Martin K. Petersen
2008-07-10 2:48 ` [PATCH 3 of 6] scsi: Support devices with protection information Martin K. Petersen
2008-07-10 2:48 ` [PATCH 4 of 6] scsi: Do not retry a request whose data integrity check failed Martin K. Petersen
2008-07-10 2:48 ` [PATCH 5 of 6] sd: Identify DIF protection type and application tag ownership Martin K. Petersen
2008-07-10 2:48 ` [PATCH 6 of 6] sd: Support for SCSI disk (SBC) Data Integrity Field Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 8:28 [PATCH 0 of 6] SCSI Data Integrity Support 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.1215658082@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--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;
as well as URLs for NNTP newsgroup(s).