NVDIMM Device and Persistent Memory development
 help / color / mirror / Atom feed
From: Tarun Sahu <tsahu@linux.ibm.com>
To: nvdimm@lists.linux.dev
Cc: tsahu@linux.ibm.com, dan.j.williams@intel.com,
	vishal.l.verma@intel.com, aneesh.kumar@linux.ibm.com,
	sbhat@linux.ibm.com, vaibhav@linux.ibm.com
Subject: [PATCH 0/2] ndctl/namespace:Fix and improve write-infoblock
Date: Wed, 13 Apr 2022 09:22:50 +0530	[thread overview]
Message-ID: <20220413035252.161527-1-tsahu@linux.ibm.com> (raw)

This series resolves some issues with write-infoblock command
and provide support to write-infoblock for sector mode namespace

write-infoblock command has issues regarding updating the align, 
uuid, parent_uuid. In case of no parameter passed for it, this command
used to overwrite the existing values with defaults. 

In PATCH 1/2 these parameters will be set to their original values, incase, 
values hasn't been passed in command arguments

write-infoblock command doesn't have support for sector/BTT mode
namespaces. They can be converted to fsdax, but can not be written
being in sector mode.

In PATCH 2/2, It creates a functionality which write infoblock of
Sector/BTT namespace. Currently only uuid, parent_uuid can be updated.
In future, Support for other parameters can easily be integrated in the
functionality.

---

Tarun Sahu (2):
  Fix multiple issues with write-infoblock command
  Implement write-infoblock for sector mode namespaces.

 ndctl/namespace.c | 297 +++++++++++++++++++++++++++++++++-------------
 ndctl/namespace.h |   7 ++
 2 files changed, 223 insertions(+), 81 deletions(-)

-- 
2.18.1


             reply	other threads:[~2022-04-13  3:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  3:52 Tarun Sahu [this message]
2022-04-13  3:52 ` [PATCH 1/2] ndctl/namespace:Fix multiple issues with write-infoblock Tarun Sahu
2022-04-25 12:37   ` Shivaprasad G Bhat
2022-04-13  3:52 ` [PATCH 2/2] ndctl/namespace:Implement write-infoblock for sector mode namespaces Tarun Sahu
2022-04-25 12:37   ` Shivaprasad G Bhat

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=20220413035252.161527-1-tsahu@linux.ibm.com \
    --to=tsahu@linux.ibm.com \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=dan.j.williams@intel.com \
    --cc=nvdimm@lists.linux.dev \
    --cc=sbhat@linux.ibm.com \
    --cc=vaibhav@linux.ibm.com \
    --cc=vishal.l.verma@intel.com \
    /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