nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@lists.01.org
Subject: [ndctl PATCH v4 0/7] Improvements for namespace creation/interrogation
Date: Mon, 05 Aug 2019 16:28:41 -0700	[thread overview]
Message-ID: <156504772175.847544.11368833704527657055.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)

Changes since v3 [1]:
- Drop the warning suppression for gcc9.1.1 the complains about taking
  the address of packed structure members. This needs a rethink since
  even the kernel's common ioctl payloads are defined to be packed. This
  will require something like the kernel's (get_unaligned()) helpers.
  (Jeff)

- Fix up a static analysis report introduced by "ndctl/dimm: Minimize
  data-transfer for init-labels"

[1]: https://lists.01.org/pipermail/linux-nvdimm/2019-August/022869.html

---

This trimmed version includes the extent support for label operations
which significantly speeds up common label operations like
'init-labels'. It also fixes up some surprising results from
'create-namespace' where it would fail even though available capacity is
present.

---

Dan Williams (7):
      ndctl/dimm: Support small label reads/writes
      ndctl/dimm: Minimize data-transfer for init-labels
      ndctl/dimm: Add offset and size options to {read,write,zero}-labels
      ndctl/dimm: Limit read-labels with --index option
      ndctl/namespace: Minimize label data transfer for autolabel
      ndctl/namespace: Continue region search on 'missing seed' event
      ndctl/namespace: Report ENOSPC when regions are full


 Documentation/ndctl/labels-options.txt    |    9 ++
 Documentation/ndctl/ndctl-read-labels.txt |    7 ++
 ndctl/dimm.c                              |   92 +++++++++++++++++--------
 ndctl/lib/dimm.c                          |   85 +++++++++++++++++++++--
 ndctl/lib/libndctl.c                      |  108 +++++++++++++++++++++++++----
 ndctl/lib/libndctl.sym                    |    9 ++
 ndctl/lib/private.h                       |    4 -
 ndctl/libndctl.h                          |    9 ++
 ndctl/namespace.c                         |   13 +++
 util/util.h                               |    4 +
 10 files changed, 285 insertions(+), 55 deletions(-)
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

             reply	other threads:[~2019-08-05 23:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 23:28 Dan Williams [this message]
2019-08-05 23:28 ` [ndctl PATCH v4 1/7] ndctl/dimm: Support small label reads/writes Dan Williams
2019-08-05 23:28 ` [ndctl PATCH v4 2/7] ndctl/dimm: Minimize data-transfer for init-labels Dan Williams
2019-08-05 23:28 ` [ndctl PATCH v4 3/7] ndctl/dimm: Add offset and size options to {read, write, zero}-labels Dan Williams
2019-08-05 23:29 ` [ndctl PATCH v4 4/7] ndctl/dimm: Limit read-labels with --index option Dan Williams
2019-08-05 23:29 ` [ndctl PATCH v4 5/7] ndctl/namespace: Minimize label data transfer for autolabel Dan Williams
2019-08-05 23:29 ` [ndctl PATCH v4 6/7] ndctl/namespace: Continue region search on 'missing seed' event Dan Williams
2019-08-05 23:29 ` [ndctl PATCH v4 7/7] ndctl/namespace: Report ENOSPC when regions are full Dan Williams

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=156504772175.847544.11368833704527657055.stgit@dwillia2-desk3.amr.corp.intel.com \
    --to=dan.j.williams@intel.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;
as well as URLs for NNTP newsgroup(s).