Linux-NVDIMM Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
	"joao.m.martins@oracle.com" <joao.m.martins@oracle.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>
Subject: Re: [PATCH daxctl v2 0/5] daxctl: range mapping allocation
Date: Sat, 19 Dec 2020 08:21:00 +0000	[thread overview]
Message-ID: <1390aa2e28e014ece1e217963ec44a0da6bd9db8.camel@intel.com> (raw)
In-Reply-To: <20201218021438.8926-1-joao.m.martins@oracle.com>

On Fri, 2020-12-18 at 02:14 +0000, Joao Martins wrote:
> Hey,
> 
> This series adds support for:
> 
>  1) Listing mappings when passing -M to ´daxctl list´. These are ommited
>  by default.
> 
>  2) Iteration APIs for the mappings.
> 
>  3) Allow passing an input JSON file with the manually selected ranges
>  to be used when creating the device-dax instance.
> 
> This applies on top of 'jm/devdax_subdiv' branch in github.com:pmem/ndctl.git
> 
> Testing requires a 5.10+ kernel.
> 
> v1 -> v2:
>   * List mappings only with -M|--mappings option
>   * Adds a unit test for --input file (while testing with -M listing too)
>   * Rename --restore to --input
>   * Add Documentation for -M and for --input
> 
> Joao Martins (5):
>   libdaxctl: add mapping iterator APIs
>   daxctl: include mappings when listing
>   libdaxctl: add daxctl_dev_set_mapping()
>   daxctl: allow creating devices from input json
>   daxctl/test: add a test for daxctl-create with input file
> 
>  Documentation/daxctl/daxctl-create-device.txt |  13 +++
>  Documentation/daxctl/daxctl-list.txt          |   4 +
>  daxctl/device.c                               | 128 +++++++++++++++++++++++++-
>  daxctl/lib/libdaxctl-private.h                |   8 ++
>  daxctl/lib/libdaxctl.c                        | 118 +++++++++++++++++++++++-
>  daxctl/lib/libdaxctl.sym                      |   7 ++
>  daxctl/libdaxctl.h                            |  14 +++
>  daxctl/list.c                                 |   4 +
>  test/daxctl-create.sh                         |  31 ++++++-
>  util/json.c                                   |  57 +++++++++++-
>  util/json.h                                   |   4 +
>  11 files changed, 380 insertions(+), 8 deletions(-)
> 
Hi Joao,

These all look good, applied. Thanks for the quick turnaround!

-Vishal
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org

      parent reply	other threads:[~2020-12-19  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18  2:14 [PATCH daxctl v2 0/5] daxctl: range mapping allocation Joao Martins
2020-12-18  2:14 ` [PATCH daxctl v2 1/5] libdaxctl: add mapping iterator APIs Joao Martins
2020-12-18  2:14 ` [PATCH daxctl v2 2/5] daxctl: include mappings when listing Joao Martins
2020-12-18  2:14 ` [PATCH daxctl v2 3/5] libdaxctl: add daxctl_dev_set_mapping() Joao Martins
2020-12-18  2:14 ` [PATCH daxctl v2 4/5] daxctl: allow creating devices from input json Joao Martins
2020-12-18  2:14 ` [PATCH daxctl v2 5/5] daxctl/test: add a test for daxctl-create with input file Joao Martins
2020-12-19  8:21 ` Verma, Vishal L [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=1390aa2e28e014ece1e217963ec44a0da6bd9db8.camel@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=joao.m.martins@oracle.com \
    --cc=linux-nvdimm@lists.01.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