From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: RE: end to end error recovery musings
Date: Wed, 28 Feb 2007 12:27:23 -0500 [thread overview]
Message-ID: <yq1tzx642h0.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <664A4EBB07F29743873A87CF62C26D705D7112@NAMAIL4.ad.lsil.com> (Eric Moore's message of "Wed, 28 Feb 2007 08:19:17 -0700")
>>>>> "Eric" == Moore, Eric <Eric.Moore@lsi.com> writes:
[Trimmed the worldwide broadcast CC: list down to linux-scsi]
Eric> I from the scsi lld perspective, all we need 32 byte cdbs, and a
Eric> mechinism to pass the tags down from above.
Ok, so your board only supports Type 2 protection?
Eric> It appears our driver to firmware insterface is only providing
Eric> the reference and application tags.
My current code allows the submitter to specify which tags are valid
between the OS and the HBA. Your inbound scsi_cmnd will have a
protection_tag_mask which tells you which fields are provided.
Similarly, there's a mask in scsi_host which allows the HBA to
identify which protection types it supports. I hadn't envisioned that
an HBA might only provide a subset. I'll ponder a bit.
Eric> I assume that for transfers greater than a sector, that the
Eric> controller firmware updates the tags for all the other sectors
Eric> within the boundary.
In other words you only support one app tag per request and not per
sector?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2007-02-28 17:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 1:10 end to end error recovery musings Moore, Eric
2007-02-27 16:50 ` Martin K. Petersen
2007-02-27 18:51 ` Ric Wheeler
2007-02-27 19:02 ` Alan
2007-02-27 18:39 ` Andreas Dilger
2007-02-27 19:07 ` Martin K. Petersen
2007-02-27 23:39 ` Alan
2007-02-27 22:51 ` Martin K. Petersen
2007-02-28 13:46 ` Douglas Gilbert
2007-02-28 17:16 ` Martin K. Petersen
2007-02-28 17:30 ` James Bottomley
2007-02-28 17:42 ` Martin K. Petersen
2007-02-28 17:52 ` James Bottomley
2007-03-01 1:28 ` H. Peter Anvin
2007-03-01 14:25 ` James Bottomley
2007-03-01 17:19 ` H. Peter Anvin
2007-02-28 15:19 ` Moore, Eric
2007-02-28 17:27 ` Martin K. Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-23 14:15 Ric Wheeler
2007-02-24 0:03 ` H. Peter Anvin
2007-02-24 0:37 ` Andreas Dilger
2007-02-24 2:05 ` H. Peter Anvin
2007-02-24 2:32 ` Theodore Tso
2007-02-24 18:39 ` Chris Wedgwood
2007-02-26 5:33 ` Neil Brown
2007-02-26 13:25 ` Theodore Tso
2007-02-26 15:15 ` Alan
2007-02-26 15:18 ` Ric Wheeler
2007-02-26 17:01 ` Alan
2007-02-26 16:42 ` Ric Wheeler
2007-02-26 15:17 ` James Bottomley
2007-02-26 18:59 ` H. Peter Anvin
2007-02-26 22:46 ` Jeff Garzik
2007-02-26 22:53 ` Ric Wheeler
2007-02-27 1:19 ` Alan
2007-02-26 6:01 ` Douglas Gilbert
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=yq1tzx642h0.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=Eric.Moore@lsi.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