nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>,
	"Hu, Fenghua" <fenghua.hu@intel.com>,
	"qi.fuli@jp.fujitsu.com" <qi.fuli@jp.fujitsu.com>
Subject: Re: [ndctl PATCH 2/7] daxctl: Documentation updates for persistent reconfiguration
Date: Wed, 17 Nov 2021 23:02:02 +0000	[thread overview]
Message-ID: <540697470a8d50b2a60862dc4c0dd79031ddb4c8.camel@intel.com> (raw)
In-Reply-To: <CAPcyv4iACg+5v=T5sqarNEfR0qChMOG0y64gzY22mtaNZVJYWg@mail.gmail.com>

On Thu, 2021-09-16 at 15:47 -0700, Dan Williams wrote:
> On Tue, Aug 31, 2021 at 2:05 AM Vishal Verma <vishal.l.verma@intel.com> wrote:
> > 
> > Add a man page update describing how daxctl-reconfigure-device(1) can
> > be used for persistent reconfiguration of a daxctl device using a
> > config file.
> > 
> > Cc: Dan Williams <dan.j.williams@intel.com>
> > Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> > ---
> >  .../daxctl/daxctl-reconfigure-device.txt      | 67 +++++++++++++++++++
> >  1 file changed, 67 insertions(+)
> > 

[snip]
(I've made all the other documentation changes suggested).

> > 
> > +
> > +[auto-online dax2]
> > +uuid = f36d02ff-1d9f-4fb9-a5b9-8ceb10a00fe3
> > +mode = system-ram
> > +online = true
> > +movable = false
> 
> One of the tasks I envisioned with persistent configurations was
> recalling resize and create device operations. Not saying that needs
> to be included now, but I can assume that these reconfiguration steps
> are performed in order... Hmm, as I ask that I realize it may depend
> on device arrival. Ok, assuming the devices have all arrived by the
> time this runs is there a guarantee that these are processed in order?

Hm, I don't quite follow what you mean by processing in order. The
logic here is that there are two 'classes' of config items in this
section - 'identification' and 'action' The uuid is the only
identification item - it is used to match the right device. The others
- 'action' items, dictate what will be done to that device. The order
here doesn't (shouldn't?) matter as these just set the param.foo fields
in daxctl/device.c, and let do_reconfig() run wild with them, just as
if the params were specified on the command line.



  reply	other threads:[~2021-11-17 23:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31  9:04 [ndctl PATCH 0/7] Policy based reconfiguration for daxctl Vishal Verma
2021-08-31  9:04 ` [ndctl PATCH 1/7] ndctl: Update ndctl.spec.in for 'ndctl.conf' Vishal Verma
2021-09-02 12:15   ` qi.fuli
2021-08-31  9:04 ` [ndctl PATCH 2/7] daxctl: Documentation updates for persistent reconfiguration Vishal Verma
2021-09-16 22:47   ` Dan Williams
2021-11-17 23:02     ` Verma, Vishal L [this message]
2021-08-31  9:04 ` [ndctl PATCH 3/7] util/parse-config: refactor filter_conf_files into util/ Vishal Verma
2021-09-02 12:17   ` qi.fuli
2021-09-16 22:54   ` Dan Williams
2021-08-31  9:04 ` [ndctl PATCH 4/7] daxctl: add basic config parsing support Vishal Verma
2021-09-02 12:19   ` qi.fuli
2021-09-16 22:58   ` Dan Williams
2021-11-17 23:17     ` Verma, Vishal L
2021-08-31  9:04 ` [ndctl PATCH 5/7] util/parse-configs: add a key/value search helper Vishal Verma
2021-09-02 13:12   ` qi.fuli
2021-09-16 23:54   ` Dan Williams
2021-11-17 23:21     ` Verma, Vishal L
2021-08-31  9:04 ` [ndctl PATCH 6/7] daxctl/device.c: add an option for getting params from a config file Vishal Verma
2021-09-17  1:59   ` Dan Williams
2021-11-17 23:45     ` Verma, Vishal L
2021-08-31  9:04 ` [ndctl PATCH 7/7] daxctl: add systemd service and udev rule for auto-onlining Vishal Verma
2021-09-03  0:56   ` qi.fuli
2021-09-17 18:10   ` Dan Williams
2021-11-17 23:29     ` Verma, Vishal L
2021-11-17 23:43       ` Dan Williams
2021-11-18  2:40     ` Verma, Vishal L
2021-11-18  3:40       ` Dan Williams
2021-09-16 22:12 ` [ndctl PATCH 0/7] Policy based reconfiguration for daxctl Dan Williams
2021-11-19 20:57   ` Verma, Vishal L

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=540697470a8d50b2a60862dc4c0dd79031ddb4c8.camel@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=fenghua.hu@intel.com \
    --cc=nvdimm@lists.linux.dev \
    --cc=qi.fuli@jp.fujitsu.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;
as well as URLs for NNTP newsgroup(s).