linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Evers <revers@redhat.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, chad.dupuis@qlogic.com,
	giridhar.malavali@qlogic.com, scameron@beardog.cce.hp.com,
	mike.miller@hp.com, fushun@marvell.com
Subject: Re: [PATCH 0/2] Change type-2 dif to use rq embedded 32 byte cdb
Date: Tue, 27 Nov 2012 11:12:17 -0500	[thread overview]
Message-ID: <50B4E661.6020002@redhat.com> (raw)
In-Reply-To: <yq14nkbsyr8.fsf@sermon.lab.mkp.net>

On 11/26/2012 06:58 PM, Martin K. Petersen wrote:
>>>>>> "Rob" == Rob Evers<revers@redhat.com>  writes:
> Rob>  These patches replace the original t10 type 2 dif mempool
> Rob>  implementation by increasing the block and scsi cdb maximum sizes
> Rob>  from 16 to 32 bytes.  The cdb embedded in the request structure can
> Rob>  then be used for type 2 dif commands, or other 32 byte cdbs as
> Rob>  required.
>
> Rob>  Motivation for this is that type-2 dif commands should be treated
> Rob>  as any other read/writes generally, without any performance
> Rob>  penalty.
>
> We did the mempool because we did not want to penalize everybody else by
> always allocating 32-byte CDBs. Type 2 is a really rare corner case.

I didn't see a penalty in the non dif case, in the sanity checking I did.
If someone has results that indicate otherwise, please indicate.

> So while I agree we should handle the UA scenario correctly, I'm not
> sure I agree with the fix. Why are you messing with Type 2 devices in
> the first place? These should really only be used inside disk arrays.
>

The previous fix for the mempool race condition was found when
one of our partners reported a problem in a system that had
type 2 dif storage attached to the host.

Use of BLK_MAX_CDB and MAX_COMMAND_SIZE could
use some feedback.



  reply	other threads:[~2012-11-27 16:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21 20:07 [PATCH 0/2] Change type-2 dif to use rq embedded 32 byte cdb Rob Evers
2012-11-21 20:07 ` [PATCH 1/2] Change the cdb size limits in block and scsi to 32 bytes Rob Evers
2012-11-21 20:07 ` [PATCH 2/2] Change dif type 2 commands to use embedded 32 byte cdb Rob Evers
2012-11-26 16:25 ` [PATCH 0/2] Change type-2 dif to use rq " Rob Evers
2012-11-26 23:58 ` Martin K. Petersen
2012-11-27 16:12   ` Rob Evers [this message]
2012-12-19 14:12 ` Rob Evers
  -- strict thread matches above, loose matches on Subject: below --
2012-12-19 10:34 Scott Guthridge
2012-12-19 16:55 ` Martin K. Petersen
2012-12-19 17:28   ` Elliott, Robert (Server Storage)
2012-12-30  0:52 ` 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=50B4E661.6020002@redhat.com \
    --to=revers@redhat.com \
    --cc=chad.dupuis@qlogic.com \
    --cc=fushun@marvell.com \
    --cc=giridhar.malavali@qlogic.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mike.miller@hp.com \
    --cc=scameron@beardog.cce.hp.com \
    /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).