From: "Javier González" <jg@lightnvm.io>
To: mb@lightnvm.io
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
"Javier González" <javier@cnexlabs.com>
Subject: [PATCH 0/2] lightnvm: patches for 4.15 on core
Date: Fri, 6 Oct 2017 15:26:23 +0200 [thread overview]
Message-ID: <1507296385-6045-1-git-send-email-javier@cnexlabs.com> (raw)
These are 2 patches on the subsystem for 4.15.
The first one is a fix on the passtrhough path that enables fail fast,
just as it is done on standard nvme passtrough commands.
The second one implements a generic way to send sync. I/O from targets.
Trough time, we ended up having _many_ wait_for_completion()
constructions to implement sync. I/O, both on pblk and at the subsystem
level. One of the main issues - besides code replication - is that we
could not benefit from improvements on blk_execute_rq to prevent hangs.
This should fix it.
Javier González (2):
lightnvm: fail fast on passthrough commands
lightnvm: implement generic path for sync I/O
drivers/lightnvm/core.c | 25 ++++++++-----
drivers/lightnvm/pblk-core.c | 78 +++++++++++++---------------------------
drivers/lightnvm/pblk-read.c | 21 ++---------
drivers/lightnvm/pblk-recovery.c | 31 ++--------------
drivers/lightnvm/pblk.h | 42 ++++++++++++++++++++--
drivers/nvme/host/lightnvm.c | 72 ++++++++++++++++++++++++++++---------
include/linux/lightnvm.h | 3 ++
7 files changed, 145 insertions(+), 127 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-06 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 13:26 Javier González [this message]
2017-10-06 13:26 ` [PATCH 1/2] lightnvm: fail fast on passthrough commands Javier González
2017-10-06 13:26 ` [PATCH 2/2] lightnvm: implement generic path for sync I/O Javier González
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=1507296385-6045-1-git-send-email-javier@cnexlabs.com \
--to=jg@lightnvm.io \
--cc=javier@cnexlabs.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.