linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: "Matias Bjørling" <mb@lightnvm.io>
Cc: "Hans Holmberg" <hans@owltronix.com>,
	"Christoph Hellwig" <hch@lst.de>,
	"Javier González" <javier@javigon.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] lnvm/pblk mapping cleanups
Date: Tue, 6 Aug 2019 14:16:12 +0000	[thread overview]
Message-ID: <a7866969-5ecc-f9e8-73b3-5dcaa79efddf@fb.com> (raw)
In-Reply-To: <5e99586b-c78c-2e70-efb0-aceef56fd19d@lightnvm.io>

On 8/6/19 6:40 AM, Matias Bjørling wrote:
> On 7/31/19 11:41 AM, Hans Holmberg wrote:
>> This series cleans up the metadata allocation/mapping in lnvm/pblk
>> by moving over to kvmalloc for metadata and moving metadata mapping
>> down to the lower lever driver where blk_rq_map_kern can be used.
>>
>> Hans Holmberg (4):
>>     lightnvm: remove nvm_submit_io_sync_fn
>>     lightnvm: move metadata mapping to lower level driver
>>     lightnvm: pblk: use kvmalloc for metadata
>>     block: stop exporting bio_map_kern
>>
>>    block/bio.c                      |   1 -
>>    drivers/lightnvm/core.c          |  43 ++++++++++++---
>>    drivers/lightnvm/pblk-core.c     | 116 +++++----------------------------------
>>    drivers/lightnvm/pblk-gc.c       |  19 +++----
>>    drivers/lightnvm/pblk-init.c     |  38 ++++---------
>>    drivers/lightnvm/pblk-read.c     |  22 +-------
>>    drivers/lightnvm/pblk-recovery.c |  39 ++-----------
>>    drivers/lightnvm/pblk-write.c    |  20 +------
>>    drivers/lightnvm/pblk.h          |  31 +----------
>>    drivers/nvme/host/lightnvm.c     |  45 +++++----------
>>    include/linux/lightnvm.h         |   8 +--
>>    11 files changed, 96 insertions(+), 286 deletions(-)
>>
> 
> Hi Jens,
> 
> Would you like me to pick up this serie, and send it through the
> lightnvm pull request, or would you like to pick it up?

I can apply it directly for 5.4.

-- 
Jens Axboe


      reply	other threads:[~2019-08-06 14:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31  9:41 [PATCH 0/4] lnvm/pblk mapping cleanups Hans Holmberg
2019-07-31  9:41 ` [PATCH 1/4] lightnvm: remove nvm_submit_io_sync_fn Hans Holmberg
2019-07-31 13:54   ` Javier González
2019-08-06  7:05   ` Christoph Hellwig
2019-07-31  9:41 ` [PATCH 2/4] lightnvm: move metadata mapping to lower level driver Hans Holmberg
2019-07-31 13:58   ` Javier González
2019-08-01  7:15     ` Hans Holmberg
2019-08-01  7:46       ` Javier González
2019-08-06  7:06   ` Christoph Hellwig
2019-07-31  9:41 ` [PATCH 3/4] lightnvm: pblk: use kvmalloc for metadata Hans Holmberg
2019-07-31 14:00   ` Javier González
2019-08-06  7:06   ` Christoph Hellwig
2019-07-31  9:41 ` [PATCH 4/4] block: stop exporting bio_map_kern Hans Holmberg
2019-07-31 17:13   ` Javier González
2019-08-06  7:07   ` Christoph Hellwig
2019-08-06 13:40 ` [PATCH 0/4] lnvm/pblk mapping cleanups Matias Bjørling
2019-08-06 14:16   ` Jens Axboe [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=a7866969-5ecc-f9e8-73b3-5dcaa79efddf@fb.com \
    --to=axboe@fb.com \
    --cc=hans@owltronix.com \
    --cc=hch@lst.de \
    --cc=javier@javigon.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@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).