[PATCH] [Target_Core_Mod 0/6] More update for genericfunctionality in v3.0

[Nicholas A. Bellinger]

Greetings all,

This patch set for Target_Core_Mod continues the process of making iSCSI
and LIO-Target specific code into generic code that is intended to be
used used across multiple $FABRIC_MODs.  This patch also includes using
kmem_cache() for se_cmd_t and se_session_t data structures, and updates
to transport_[register,deregister]_session().

Also included is a change to the Target_Core_Mod/PSCSI subsystem plugin
for v2.6.28 that involves setting struct bio->bi_bdev w/o
bio_add_pc_page() now that scsi_execute_async() have been removed for
v2.6.28-FINAL.

They are made against against lio-core-2.6.git/master and tested on
v2.6.28-rc7.  The lio-core-2.6.git tree can be found at:

http://git.kernel.org/?p=linux/kernel/git/nab/lio-core-2.6.git;a=summary

--nab

 drivers/lio-core/target_core_base.h       |   32 +++--
 drivers/lio-core/target_core_device.c     |   44 +++++-
 drivers/lio-core/target_core_device.h     |    1 +
 drivers/lio-core/target_core_fabric_ops.h |    6 +-
 drivers/lio-core/target_core_pscsi.c      |   36 ++++-
 drivers/lio-core/target_core_pscsi.h      |    1 +
 drivers/lio-core/target_core_tpg.c        |   20 ++-
 drivers/lio-core/target_core_tpg.h        |    4 +-
 drivers/lio-core/target_core_transport.c  |  247 +++++++++++++++--------------
 drivers/lio-core/target_core_transport.h  |    6 +-
 10 files changed, 249 insertions(+), 148 deletions(-)

[PATCH] [Target_Core_Mod 1/6] Updates for core data structures
[PATCH] [Target_Core_Mod 2/6]: Update struct target_core_fabric_ops
[PATCH] [Target_Core_Mod 3/6]: Updates for transport_[register,deregister]_session() logic
[PATCH] [Target_Core_Mod 4/6]: Updates for generic portal group functionality
[PATCH] [Target_Core_Mod 5/6]: Updates for generic device core
[PATCH] [Target_Core_Mod/PSCSI 6/6]: Grab temporary pointer to struct block_device for BIO for v2.6.28


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