public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen M. Cameron" <scameron@beardog.cce.hp.com>
To: axboe@kernel.dk, akpm@linux-foundation.org, james.bottomley@suse.de
Cc: linux-kernel@vger.kernel.org, mikem@beardog.cce.hp.com,
	linux-scsi@vger.kernel.org, brace@beardog.cce.hp.com
Subject: [PATCH 0/9] cciss driver SCSI updates
Date: Fri, 26 Feb 2010 16:01:06 -0600	[thread overview]
Message-ID: <20100226220023.11979.4999.stgit@beardog.cce.hp.com> (raw)

The following series mainly fixes the scsi tape code in the cciss
driver to take advantage of more scatter gather elements, enabling
larger transfer sizes.  The first eight patches are mainly cleaning
things up and getting ready for the 9th patch, which enables the
SCSI half of the driver to use more than 31 scatter gather elements.

I've tested on 32-bit and 64-bit systems, and written out tapes
with block sizes up to 2Mb.

These patches are vs. Jens's linux-2.6-block tree.

Stephen M. Cameron (9):
      cciss: clarify command list padding calculation
      cciss: detect bad alignment of scsi commands at build time
      cciss: factor out scatter gather chain block allocation and freeing
      cciss: simplify scatter gather code
      cciss: fix scatter gather chain block dma direction kludge
      cciss: factor out scatter gather chain block mapping code
      cciss: do not use void pointer for scsi hba data
      cciss: eliminate unnecessary pointer use in cciss scsi code
      cciss: Fix problem with scatter gather elements in the scsi half of the driver


 drivers/block/cciss.c      |  174 ++++++++++++++++++++++----------------------
 drivers/block/cciss.h      |   12 +--
 drivers/block/cciss_cmd.h  |   14 +++-
 drivers/block/cciss_scsi.c |  145 +++++++++++++++++++++++--------------
 4 files changed, 188 insertions(+), 157 deletions(-)

-- 
-- steve

             reply	other threads:[~2010-02-26 22:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 22:01 Stephen M. Cameron [this message]
2010-02-26 22:01 ` [PATCH 1/9] cciss: clarify command list padding calculation Stephen M. Cameron
2010-02-26 22:01 ` [PATCH 2/9] cciss: detect bad alignment of scsi commands at build time Stephen M. Cameron
2010-02-26 22:01 ` [PATCH 3/9] cciss: factor out scatter gather chain block allocation and freeing Stephen M. Cameron
2010-02-26 22:01 ` [PATCH 4/9] cciss: simplify scatter gather code Stephen M. Cameron
2010-02-26 22:01 ` [PATCH 5/9] cciss: fix scatter gather chain block dma direction kludge Stephen M. Cameron
2010-02-26 22:01 ` [PATCH 6/9] cciss: factor out scatter gather chain block mapping code Stephen M. Cameron
2010-02-26 22:01 ` [PATCH 7/9] cciss: do not use void pointer for scsi hba data Stephen M. Cameron
2010-02-26 22:01 ` [PATCH 8/9] cciss: eliminate unnecessary pointer use in cciss scsi code Stephen M. Cameron
2010-02-26 22:01 ` [PATCH 9/9] cciss: Fix problem with scatter gather elements in the scsi half of the driver Stephen M. Cameron
2010-02-28 18:43 ` [PATCH 0/9] cciss driver SCSI updates Jens Axboe

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=20100226220023.11979.4999.stgit@beardog.cce.hp.com \
    --to=scameron@beardog.cce.hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=brace@beardog.cce.hp.com \
    --cc=james.bottomley@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mikem@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