linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Holmberg <hans@owltronix.com>
To: "Matias Bjørling" <mb@lightnvm.io>
Cc: "Igor Konopko" <igor.j.konopko@intel.com>,
	"Javier González" <javier@javigon.com>,
	linux-block@vger.kernel.org
Subject: Re: [PATCH v5 0/3] lightnvm: next set of improvements for 5.2
Date: Mon, 29 Apr 2019 07:13:24 -0400	[thread overview]
Message-ID: <CANr-nt0c-4H5PfaH=b-CPrLbMhs=r4skr-oskOGQsyNB=gOMug@mail.gmail.com> (raw)
In-Reply-To: <087e8d6e-8cdc-87ff-6e2f-cb1fa2fd0396@lightnvm.io>

On Fri, Apr 26, 2019 at 3:54 PM Matias Bjørling <mb@lightnvm.io> wrote:
>
> Thanks Igor. I've picked up 1 + 2.
>
> The third I'm still noodling on. I think maybe one should bump the disk
> format, since it's changed. Also, if it is, it should be a static setup
> (i.e., 1,2,3), and not user configurable. Although, I do expect the
> separate parallel units to have enough device-side redundancy to provide
> adequate UBER.

The change is backwards- and forwards-compatible (a disk written with
both an older and a newer
kernel would be readable, since smeta sectors are marked as ADD_EMPTY)
 as far as I can tell,
buy did you test this Igor?

I think we might as well bump SMETA_VERSION_MINOR anyway, so we can keep
track of this format change for the future(i.e if we build an offline
recovery tool)

Thanks,
Hans
>
>
>
> On 4/26/19 3:35 PM, Igor Konopko wrote:
> > This is another set of fixes and improvements to both pblk and lightnvm
> > core.
> >
> > Changes v4 -> v5:
> > -dropped patches which were already pulled into for-5.2/core branch
> > -rebasing of other patches
> > -multiple copies of smeta patch moved into last position in series
> > so it would be easier to pull only previous patches if needed
> >
> > Changes v3 -> v4:
> > -dropped patches which were already pulled into for-5.2/core branch
> > -major changes for patch #2 based on code review
> > -patch #6 modified to use krefs
> > -new patch #7 which extends the patch #6
> >
> > Changes v2 -> v3:
> > -dropped some not needed patches
> > -dropped patches which were already pulled into for-5.2/core branch
> > -commit messages cleanup
> >
> > Changes v1 -> v2:
> > -dropped some not needed patches
> > -review feedback incorporated for some of the patches
> > -partial read path changes patch splited into two patches
> >
> >
> > Igor Konopko (3):
> >    lightnvm: pblk: simplify partial read path
> >    lightnvm: pblk: use nvm_rq_to_ppa_list()
> >    lightnvm: pblk: store multiple copies of smeta
> >
> >   drivers/lightnvm/pblk-core.c     | 159 ++++++++++++++----
> >   drivers/lightnvm/pblk-init.c     |  23 ++-
> >   drivers/lightnvm/pblk-rb.c       |  11 +-
> >   drivers/lightnvm/pblk-read.c     | 339 ++++++++++-----------------------------
> >   drivers/lightnvm/pblk-recovery.c |  27 ++--
> >   drivers/lightnvm/pblk-rl.c       |   3 +-
> >   drivers/lightnvm/pblk.h          |  19 +--
> >   7 files changed, 252 insertions(+), 329 deletions(-)
> >
>

  reply	other threads:[~2019-04-29 11:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26 13:35 [PATCH v5 0/3] lightnvm: next set of improvements for 5.2 Igor Konopko
2019-04-26 13:35 ` [PATCH v5 1/3] lightnvm: pblk: simplify partial read path Igor Konopko
2019-04-26 16:30   ` Heiner Litz
2019-05-01  6:20   ` Javier González
2019-04-26 13:35 ` [PATCH v5 2/3] lightnvm: pblk: use nvm_rq_to_ppa_list() Igor Konopko
2019-04-26 13:35 ` [PATCH v5 3/3] lightnvm: pblk: store multiple copies of smeta Igor Konopko
2019-04-26 19:53 ` [PATCH v5 0/3] lightnvm: next set of improvements for 5.2 Matias Bjørling
2019-04-29 11:13   ` Hans Holmberg [this message]
2019-05-02 10:03     ` Igor Konopko

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='CANr-nt0c-4H5PfaH=b-CPrLbMhs=r4skr-oskOGQsyNB=gOMug@mail.gmail.com' \
    --to=hans@owltronix.com \
    --cc=igor.j.konopko@intel.com \
    --cc=javier@javigon.com \
    --cc=linux-block@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).