From: Rob Evers <revers@redhat.com>
To: linux-scsi@vger.kernel.org
Cc: chad.dupuis@qlogic.com, giridhar.malavali@qlogic.com,
scameron@beardog.cce.hp.com, mike.miller@hp.com,
dan.j.williams@intel.com, fushun@marvell.com
Subject: [PATCH 1/2] Change the cdb size limits in block and scsi to 32 bytes
Date: Wed, 21 Nov 2012 15:07:47 -0500 [thread overview]
Message-ID: <1353528468-5664-2-git-send-email-revers@redhat.com> (raw)
In-Reply-To: <1353528468-5664-1-git-send-email-revers@redhat.com>
Signed-off-by: Rob Evers <revers@redhat.com>
---
include/linux/blkdev.h | 2 +-
include/scsi/scsi_cmnd.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index 1756001..cafce6e 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -85,7 +85,7 @@ enum rq_cmd_type_bits {
REQ_TYPE_ATA_PC,
};
-#define BLK_MAX_CDB 16
+#define BLK_MAX_CDB 32
/*
* try to put the fields that are referenced together in the same cacheline.
diff --git a/include/scsi/scsi_cmnd.h b/include/scsi/scsi_cmnd.h
index de5f5d8..9890d29 100644
--- a/include/scsi/scsi_cmnd.h
+++ b/include/scsi/scsi_cmnd.h
@@ -24,7 +24,7 @@ struct scsi_driver;
* So in effect MAX_COMMAND_SIZE means the maximum size command scsi-ml
* supports without specifying a cmd_len by ULD's
*/
-#define MAX_COMMAND_SIZE 16
+#define MAX_COMMAND_SIZE 32
#if (MAX_COMMAND_SIZE > BLK_MAX_CDB)
# error MAX_COMMAND_SIZE can not be bigger than BLK_MAX_CDB
#endif
--
1.7.11.7
next prev parent reply other threads:[~2012-11-21 20:08 UTC|newest]
Thread overview: 7+ 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 ` Rob Evers [this message]
2012-11-21 20:07 ` [PATCH 2/2] Change dif type 2 commands to use " 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
2012-12-19 14:12 ` Rob Evers
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=1353528468-5664-2-git-send-email-revers@redhat.com \
--to=revers@redhat.com \
--cc=chad.dupuis@qlogic.com \
--cc=dan.j.williams@intel.com \
--cc=fushun@marvell.com \
--cc=giridhar.malavali@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--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).