From: "Matias Bjørling" <mb@lightnvm.io>
To: javier@javigon.com
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, javier@cnexlabs.com
Subject: Re: [PATCH 3/3] lightnvm: pblk: take write semaphore on metadata
Date: Wed, 29 Aug 2018 15:08:10 +0200 [thread overview]
Message-ID: <f4f8c276-0269-5aa5-39fc-42aecc7bb309@lightnvm.io> (raw)
In-Reply-To: <1535532980-27672-4-git-send-email-javier@cnexlabs.com>
On 08/29/2018 10:56 AM, Javier González wrote:
> pblk guarantees write ordering at a chunk level through a per open chunk
> semaphore. At this point, since we only have an open I/O stream for both
> user and GC data, the semaphore is per parallel unit.
>
> For the metadata I/O that is synchronous, the semaphore is not needed as
> ordering is guaranteed. However, if the metadata scheme changes or
> multiple streams are open, this guarantee might not be preserved.
>
> This patch makes sure that all writes go through the semaphore, even for
> synchronous I/O. This is consistent with pblk's write I/O model. It also
> simplifies maintenance since changes in the metadata scheme could cause
> ordering issues.
>
> Signed-off-by: Javier González <javier@cnexlabs.com>
> ---
> drivers/lightnvm/pblk-core.c | 16 +++++++++++++++-
> drivers/lightnvm/pblk.h | 1 +
> 2 files changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/lightnvm/pblk-core.c b/drivers/lightnvm/pblk-core.c
> index 767178185f19..1e4dc0c1ed88 100644
> --- a/drivers/lightnvm/pblk-core.c
> +++ b/drivers/lightnvm/pblk-core.c
> @@ -558,6 +558,20 @@ int pblk_submit_io_sync(struct pblk *pblk, struct nvm_rq *rqd)
> return ret;
> }
>
> +int pblk_submit_io_sync_sem(struct pblk *pblk, struct nvm_rq *rqd)
> +{
> + struct ppa_addr *ppa_list;
> + int ret;
> +
> + ppa_list = (rqd->nr_ppas > 1) ? rqd->ppa_list : &rqd->ppa_addr;
> +
> + pblk_down_page(pblk, ppa_list, rqd->nr_ppas);
If the debug stuff is killed inside __pblk_down_page, then ppa_list and
rqd->nr_ppas does not need to be passed, and this function can be
inlined in its caller. Can we kill it? I'll make the patch if you like.
> + ret = pblk_submit_io_sync(pblk, rqd);
> + pblk_up_page(pblk, ppa_list, rqd->nr_ppas);
> +
> + return ret;
> +}
> +
> static void pblk_bio_map_addr_endio(struct bio *bio)
> {
> bio_put(bio);
> @@ -788,7 +802,7 @@ static int pblk_line_smeta_write(struct pblk *pblk, struct pblk_line *line,
> meta_list[i].lba = lba_list[paddr] = addr_empty;
> }
>
> - ret = pblk_submit_io_sync(pblk, &rqd);
> + ret = pblk_submit_io_sync_sem(pblk, &rqd);
> if (ret) {
> pblk_err(pblk, "smeta I/O submission failed: %d\n", ret);
> bio_put(bio);
> diff --git a/drivers/lightnvm/pblk.h b/drivers/lightnvm/pblk.h
> index c0d9eddd344b..54f937c1fb62 100644
> --- a/drivers/lightnvm/pblk.h
> +++ b/drivers/lightnvm/pblk.h
> @@ -793,6 +793,7 @@ void pblk_log_write_err(struct pblk *pblk, struct nvm_rq *rqd);
> void pblk_log_read_err(struct pblk *pblk, struct nvm_rq *rqd);
> int pblk_submit_io(struct pblk *pblk, struct nvm_rq *rqd);
> int pblk_submit_io_sync(struct pblk *pblk, struct nvm_rq *rqd);
> +int pblk_submit_io_sync_sem(struct pblk *pblk, struct nvm_rq *rqd);
> int pblk_submit_meta_io(struct pblk *pblk, struct pblk_line *meta_line);
> void pblk_check_chunk_state_update(struct pblk *pblk, struct nvm_rq *rqd);
> struct bio *pblk_bio_map_addr(struct pblk *pblk, void *data,
>
next prev parent reply other threads:[~2018-08-29 13:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 8:56 [V4 PATCH 0/2] " Javier González
2018-08-29 8:56 ` [PATCH 1/3] lightnvm: pblk: refactor metadata paths Javier González
2018-08-29 13:02 ` Matias Bjørling
2018-08-29 13:19 ` Javier Gonzalez
2018-08-29 8:56 ` [PATCH 2/3] lightnvm: encapsule rqd dma allocations Javier González
2018-08-29 13:00 ` Matias Bjørling
2018-08-29 13:18 ` Javier Gonzalez
2018-08-29 13:36 ` Matias Bjørling
2018-08-29 13:41 ` Javier Gonzalez
2018-08-29 13:42 ` Matias Bjørling
2018-08-29 8:56 ` [PATCH 3/3] lightnvm: pblk: take write semaphore on metadata Javier González
2018-08-29 13:08 ` Matias Bjørling [this message]
2018-08-29 13:21 ` Javier Gonzalez
2018-08-29 13:40 ` Matias Bjørling
2018-08-29 13:41 ` Javier Gonzalez
2018-09-11 11:24 [V5 PATCH 0/3] " Javier González
2018-09-11 11:24 ` [PATCH 3/3] " 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=f4f8c276-0269-5aa5-39fc-42aecc7bb309@lightnvm.io \
--to=mb@lightnvm.io \
--cc=axboe@kernel.dk \
--cc=javier@cnexlabs.com \
--cc=javier@javigon.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®