Question about submitting large patchset for hpsa driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi James,

I have a large patch set for hpsa that's been brewing for awhile
and it's finally stabilized.  I notice you have a for-next
and misc branches that are slightly different, and was wondering
which branch of your tree you'd prefer the patches be tailored for,
or if you'd prefer I hold off until after 3.13 comes out, or
maybe something else?

Diffstat of the combined 40 or so patches I have brewing looks like:

 Documentation/ABI/testing/sysfs-class-scsi_host |   16 
 drivers/scsi/hpsa.c                             | 2544 ++++++++++++++++++++----
 drivers/scsi/hpsa.h                             |  138 +
 drivers/scsi/hpsa_cmd.h                         |  255 ++
 4 files changed, 2566 insertions(+), 387 deletions(-)

The thrust of the patch set is to enable a couple alternate ways
of submitting commands directly to physical devices, kind of
going around the normal Smart Array firmware RAID stack for
certain i/o's in order to get a pretty substantial performance
gain when using SSDs.

-- steve

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux