On 11/18/2016 03:43 PM, Javier González wrote: > This patchset simplifies the generic media manager interface and moves > lun and block functionality to lightnvm targets. This makes that > rrpc-specific functionality is not exposed on the media manager. This is > done in preparation for the pblk target. > > Matias: patches 0 - 4 have been posted before. Patches apply to you > for-4.10/core > > Javier González (20): > lightnvm: enable to send hint to erase command > lightnvm: do not protect block 0 > lightnvm: export set bad block table > lightnvm: add ECC error codes > lightnvm: rrpc: split bios of size > 256kb > lightnvm: remove sysfs configuration interface > lightnvm: cleanup unused target operations > lightnvm: make address conversion functions global > lightnvm: remove unnecessary variables in rrpc > lightnvm: use constant name instead of value > lightnvm: remove gen_lun abstraction > lightnvm: manage lun partitions internally in mm > lightnvm: move block provisioning to targets > lightnvm: remove get_lun operation on gennvm > lightnvm: remove debug lun statistics from gennvm > lightnvm: eliminate nvm_block abstraction on mm > lightnvm: eliminate nvm_lun abstraction in mm > lightnvm: introduce helpers for generic ops in rrpc > lightnvm: introduce max_phys_sects helper function > lightnvm: use target nvm on target-specific ops. > > drivers/lightnvm/core.c | 306 ++++++++------------ > drivers/lightnvm/gennvm.c | 664 ++++++++++++++++++++----------------------- > drivers/lightnvm/gennvm.h | 34 ++- > drivers/lightnvm/rrpc.c | 512 +++++++++++++++++++++------------ > drivers/lightnvm/rrpc.h | 65 ++++- > drivers/lightnvm/sysblk.c | 98 +++---- > drivers/nvme/host/lightnvm.c | 15 +- > include/linux/lightnvm.h | 231 +++++++-------- > 8 files changed, 1005 insertions(+), 920 deletions(-) > Thanks Javier. I have picked 1-12 (including "manage lun partitions internally in mm"). Will wait on repost of 13-20 to pick the rest. -- To unsubscribe from this list: send the line "unsubscribe linux-block" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
