From: "Javier González" <javier@javigon.com>
To: mb@lightnvm.io
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Javier González" <javier@cnexlabs.com>
Subject: [V5 PATCH 0/3] lightnvm: pblk: take write semaphore on metadata
Date: Tue, 11 Sep 2018 13:24:48 +0200 [thread overview]
Message-ID: <1536665091-12641-1-git-send-email-javier@cnexlabs.com> (raw)
# Changes since V4:
- Rebase on top of Matias' core
- Reorder patches to avoid in-patchset changes
# Changes since V3:
- Encapsulate rqd dma allocations to reduce code replication (by Matias)
# Changes since V2:
- Split the original patch between the metadata refactoring and the
semaphore logic. This simplifies the write path, where the semaphore
is taken.
# Changes singe V1:
- Fix double I/O on the read path (by Matias)
- Improve commit message (by Jens)
This patchset refactors the metadata separate write and read paths,
which simplifies how the semaphore is taken for writes.
Thanks,
Javier
Javier González (3):
lightnvm: encapsule rqd dma allocations
lightnvm: pblk: refactor metadata paths
lightnvm: pblk: take write semaphore on metadata
drivers/lightnvm/pblk-core.c | 376 ++++++++++++++++++++-------------------
drivers/lightnvm/pblk-gc.c | 2 +-
drivers/lightnvm/pblk-read.c | 31 ++--
drivers/lightnvm/pblk-recovery.c | 34 ++--
drivers/lightnvm/pblk-write.c | 15 +-
drivers/lightnvm/pblk.h | 7 +-
6 files changed, 222 insertions(+), 243 deletions(-)
--
2.7.4
next reply other threads:[~2018-09-11 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 11:24 Javier González [this message]
2018-09-11 11:24 ` [PATCH 1/3] lightnvm: encapsule rqd dma allocations Javier González
2018-09-11 11:24 ` [PATCH 2/3] lightnvm: pblk: refactor metadata paths Javier González
2018-09-11 11:24 ` [PATCH 3/3] lightnvm: pblk: take write semaphore on metadata Javier González
2018-09-17 8:11 ` [V5 PATCH 0/3] " Matias Bjørling
2018-09-17 10:11 ` Javier Gonzalez
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=1536665091-12641-1-git-send-email-javier@cnexlabs.com \
--to=javier@javigon.com \
--cc=axboe@kernel.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).