From: Wenwei Tao <ww.tao0320@gmail.com>
To: mb@lightnvm.io, keith.busch@intel.com, axboe@fb.com
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: [PATCH v2 0/3] fixes for LightNVM
Date: Fri, 27 Nov 2015 12:09:41 +0800 [thread overview]
Message-ID: <1448597384-27976-1-git-send-email-ww.tao0320@gmail.com> (raw)
Hi Matias
A couple of fixes based on 4.4rc2
Patch 1: the locking issue
move codes 'register with device with a supported manager'
into a funtion.
But I think iterate over a list to register nvm device
with a manger is not a good idea, since we can blocked
in manager's register_mgr function while holding nvm_lock.
Patch 2: handle targerts when underlying devices were removed
free dev when exited
call target type's exit function when target creation was aborted
due to nvm device exit.
Patch 3: change the interface between nvme and lightnvm
remove the unnecessary nvme_ns->type set to zero
Wenwei Tao (3):
lightnvm: missing nvm_lock acquire
lightnvm: handle targets when corresponding nvm device exit
nvme: change the interface between nvme and lightnvm
drivers/lightnvm/core.c | 197 ++++++++++++++++++++++++++-----------------
drivers/nvme/host/lightnvm.c | 17 +++-
drivers/nvme/host/nvme.h | 1 +
drivers/nvme/host/pci.c | 7 +-
include/linux/lightnvm.h | 3 +
5 files changed, 143 insertions(+), 82 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-11-27 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 4:09 Wenwei Tao [this message]
2015-11-27 4:09 ` [PATCH v2 1/3] lightnvm: missing nvm_lock acquire Wenwei Tao
2015-11-27 8:31 ` Matias Bjørling
2015-11-27 12:04 ` Wenwei Tao
2015-11-27 19:41 ` Matias Bjørling
2015-11-28 1:44 ` Wenwei Tao
2015-11-27 4:09 ` [PATCH v2 2/3] lightnvm: handle targets when corresponding nvm device exit Wenwei Tao
2015-11-27 4:09 ` [PATCH v2 3/3] nvme: change the interface between nvme and lightnvm Wenwei Tao
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=1448597384-27976-1-git-send-email-ww.tao0320@gmail.com \
--to=ww.tao0320@gmail.com \
--cc=axboe@fb.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mb@lightnvm.io \
/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
all inboxes | Powered by JetHome®