mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Igor Konopko <igor.j.konopko@intel.com>
To: "Javier González" <javier@javigon.com>, mb@lightnvm.io
Cc: marcin.dziegielewski@intel.com, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Javier González" <javier@cnexlabs.com>
Subject: Re: [PATCH 0/3] lightnvm: pblk: support variable OOB size
Date: Wed, 29 Aug 2018 16:51:06 +0200	[thread overview]
Message-ID: <106d492e-4f09-7af5-d89a-75c204f3da38@intel.com> (raw)
In-Reply-To: <1535537370-10729-1-git-send-email-javier@cnexlabs.com>



On 29.08.2018 12:09, Javier González wrote:
> This patchset adds pblk support for variable metadata sizes on the out
> of bound area.
> 
> Igor, Marcin, you sent a patch some time ago implementing a similar
> functionality, but it never got re-posted after review. Can you test
> this and see if it works for your case? I did not implement support for
> outlined metadata for the case where the reported OOB area is 0. It
> should be pretty simple to do that on top of these patches though.
> 

Sure, we will test that and let you know. I was busy last time and due 
to that I never repost it. I will do this on top of your patches, 
hopefully soon.

> Thanks,
> Javier
> 
> Javier González (3):
>    lightnvm: use internal allocation for chunk log page
>    lightnvm: do no update csecs and sos on 1.2
>    lightnvm: pblk: support variable OOB size
> 
>   drivers/lightnvm/pblk-core.c     | 60 ++++++++++++++++++++++++++++++----------
>   drivers/lightnvm/pblk-init.c     | 16 ++++++++++-
>   drivers/lightnvm/pblk-map.c      | 19 +++++++++----
>   drivers/lightnvm/pblk-read.c     | 55 ++++++++++++++++++++++--------------
>   drivers/lightnvm/pblk-recovery.c | 34 ++++++++++++++++-------
>   drivers/lightnvm/pblk.h          | 18 +++++++++---
>   drivers/nvme/host/lightnvm.c     | 26 +++++++++++------
>   7 files changed, 164 insertions(+), 64 deletions(-)
> 

  parent reply	other threads:[~2018-08-29 14:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 10:09 Javier González
2018-08-29 10:09 ` [PATCH 1/3] lightnvm: use internal allocation for chunk log page Javier González
2018-09-07 10:38   ` Matias Bjørling
2018-09-07 12:53   ` Hans Holmberg
2018-09-07 15:12     ` Matias Bjørling
2018-08-29 10:09 ` [PATCH 2/3] lightnvm: do no update csecs and sos on 1.2 Javier González
2018-09-07 10:28   ` Matias Bjørling
2018-09-11  8:50     ` Javier Gonzalez
2018-09-11 11:30       ` Javier Gonzalez
2018-09-18  8:37         ` Matias Bjørling
2018-08-29 10:09 ` [PATCH 3/3] lightnvm: pblk: support variable OOB size Javier González
2018-09-10 10:21   ` Matias Bjørling
2018-09-11  9:14     ` Javier Gonzalez
2018-09-11 10:22       ` Igor Konopko
2018-09-18  8:09         ` Javier Gonzalez
2018-09-18  8:31           ` Matias Bjørling
2018-09-18  8:32             ` Javier Gonzalez
2018-10-05 12:18               ` Javier Gonzalez
2018-10-09  9:16                 ` Matias Bjørling
2018-10-09 12:31                   ` Javier Gonzalez
2018-08-29 14:51 ` Igor Konopko [this message]
2018-08-29 19:57   ` [PATCH 0/3] " 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=106d492e-4f09-7af5-d89a-75c204f3da38@intel.com \
    --to=igor.j.konopko@intel.com \
    --cc=javier@cnexlabs.com \
    --cc=javier@javigon.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.dziegielewski@intel.com \
    --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

all inboxes | Powered by JetHome®