mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Matias Bjørling" <mb@lightnvm.io>
To: "Javier González" <javier@javigon.com>
Cc: jg@lightnvm.io, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org,
	"Javier González" <javier@cnexlabs.com>
Subject: Re: [PATCH 1/2] lightnvm: let rrpc block know its rrpc lun
Date: Thu, 7 Jan 2016 13:51:58 +0100	[thread overview]
Message-ID: <568E5F6E.5070802@lightnvm.io> (raw)
In-Reply-To: <1452168205-5559-1-git-send-email-javier@javigon.com>

On 01/07/2016 01:03 PM, Javier González wrote:
> Currently a rrpc block only points to the nvm_lun it belongs to.
> Maintaining a reference to the rrpc lun allows to manage rrpc specific
> behavior between an rrpc block and rrpc lun.
>
> Signed-off-by: Javier González <javier@cnexlabs.com>
> ---
>   drivers/lightnvm/rrpc.c | 1 +
>   drivers/lightnvm/rrpc.h | 1 +
>   2 files changed, 2 insertions(+)
>
> diff --git a/drivers/lightnvm/rrpc.c b/drivers/lightnvm/rrpc.c
> index ec7aacf..1bea346 100644
> --- a/drivers/lightnvm/rrpc.c
> +++ b/drivers/lightnvm/rrpc.c
> @@ -1150,6 +1150,7 @@ static int rrpc_luns_init(struct rrpc *rrpc, int lun_begin, int lun_end)
>   			struct nvm_block *blk = &lun->blocks[j];
>
>   			rblk->parent = blk;
> +			rblk->rlun = rlun;
>   			INIT_LIST_HEAD(&rblk->prio);
>   			spin_lock_init(&rblk->lock);
>   		}
> diff --git a/drivers/lightnvm/rrpc.h b/drivers/lightnvm/rrpc.h
> index a9696a0..7c5fa4d 100644
> --- a/drivers/lightnvm/rrpc.h
> +++ b/drivers/lightnvm/rrpc.h
> @@ -54,6 +54,7 @@ struct rrpc_rq {
>
>   struct rrpc_block {
>   	struct nvm_block *parent;
> +	struct rrpc_lun *rlun;
>   	struct list_head prio;
>
>   #define MAX_INVALID_PAGES_STORAGE 8
>

Thanks, applied for 4.5. I've slightly changed the patch text.

      parent reply	other threads:[~2016-01-07 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07 12:03 Javier González
2016-01-07 12:03 ` [PATCH 2/2] lightnvm: manage open and closed blocks separately Javier González
2016-01-07 12:51 ` Matias Bjørling [this message]

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=568E5F6E.5070802@lightnvm.io \
    --to=mb@lightnvm.io \
    --cc=javier@cnexlabs.com \
    --cc=javier@javigon.com \
    --cc=jg@lightnvm.io \
    --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

Powered by JetHome