From: "Matias Bjørling" <mb@lightnvm.io>
To: Wenwei Tao <ww.tao0320@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] lightnvm: move the pages per block check out of the loop
Date: Tue, 5 Jan 2016 12:46:37 +0100 [thread overview]
Message-ID: <568BAD1D.3090306@lightnvm.io> (raw)
In-Reply-To: <1451994218-5871-1-git-send-email-ww.tao0320@gmail.com>
On 01/05/2016 12:43 PM, Wenwei Tao wrote:
> There is no need to check whether dev's pages per block is
> beyond rrpc support everytime we init a lun, we only need
> to check it once before enter the lun init loop.
>
> Signed-off-by: Wenwei Tao <ww.tao0320@gmail.com>
> ---
> drivers/lightnvm/rrpc.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/lightnvm/rrpc.c b/drivers/lightnvm/rrpc.c
> index 27fb98d..286a038 100644
> --- a/drivers/lightnvm/rrpc.c
> +++ b/drivers/lightnvm/rrpc.c
> @@ -1087,6 +1087,11 @@ static int rrpc_luns_init(struct rrpc *rrpc, int lun_begin, int lun_end)
> struct rrpc_lun *rlun;
> int i, j;
>
> + if (dev->pgs_per_blk > MAX_INVALID_PAGES_STORAGE * BITS_PER_LONG) {
> + pr_err("rrpc: number of pages per block too high.");
> + return -EINVAL;
> + }
> +
> spin_lock_init(&rrpc->rev_lock);
>
> rrpc->luns = kcalloc(rrpc->nr_luns, sizeof(struct rrpc_lun),
> @@ -1098,12 +1103,6 @@ static int rrpc_luns_init(struct rrpc *rrpc, int lun_begin, int lun_end)
> for (i = 0; i < rrpc->nr_luns; i++) {
> struct nvm_lun *lun = dev->mt->get_lun(dev, lun_begin + i);
>
> - if (dev->pgs_per_blk >
> - MAX_INVALID_PAGES_STORAGE * BITS_PER_LONG) {
> - pr_err("rrpc: number of pages per block too high.");
> - goto err;
> - }
> -
> rlun = &rrpc->luns[i];
> rlun->rrpc = rrpc;
> rlun->parent = lun;
>
Thanks. Leftover from when luns could have different number of pages.
Applied for 4.5.
prev parent reply other threads:[~2016-01-05 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 11:43 Wenwei Tao
2016-01-05 11:46 ` 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=568BAD1D.3090306@lightnvm.io \
--to=mb@lightnvm.io \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ww.tao0320@gmail.com \
/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