All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Busch, Keith" <keith.busch@intel.com>
Cc: "y-goto@jp.fujitsu.com" <y-goto@jp.fujitsu.com>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] ndctl: Use max_available_extent for creating namespaces
Date: Tue, 26 Jun 2018 16:27:36 +0000	[thread overview]
Message-ID: <1530030454.27147.23.camel@intel.com> (raw)
In-Reply-To: <20180626162924.GB6754@localhost.localdomain>

On Tue, 2018-06-26 at 10:29 -0600, Keith Busch wrote:
> On Tue, Jun 26, 2018 at 09:19:28AM -0700, Verma, Vishal L wrote:
> > On Tue, 2018-06-26 at 09:37 -0600, Keith Busch wrote:
> > > The available_size attribute returns all the unused regions, but a
> > > namespace has to use contiguous free regions. This patch uses the
> > > attribute returning the largest capacity that can be created for
> > > determining if the namespace can be created.
> > > 
> > > Signed-off-by: Keith Busch <keith.busch@intel.com>
> > > ---
> > >  ndctl/lib/libndctl.c   | 30 ++++++++++++++++++++++++++++++
> > >  ndctl/lib/libndctl.sym |  1 +
> > >  ndctl/libndctl.h       |  2 ++
> > >  ndctl/namespace.c      |  2 +-
> > >  4 files changed, 34 insertions(+), 1 deletion(-)
> > 
> > Hi Keith,
> > 
> > The patch looks good, but just a couple of 'meta' comments.
> > 1. We typically send ndctl patches separately from kernel patches (i.e.
> > not
> > thraded together).
> > 2. for ndctl patches, an 'ndctl PATCH' prefix is recommended. You can
> > set a
> > repo local config parameter for doing this automatically on git format-
> > patch.
> > 	git config format.subjectprefix "ndctl PATCH"
> > 
> > I'm thinking the kernel changes will be queued for 4.19, which means
> > the
> > ndctl changes will go into v62.
> 
> Thanks for the info. I'll make those changes for next time.
> 
> I think I may need to send a v2 for this. Should we have this fall back
> to
> the available_size for the older kernels where the max_available_extents
> attribute is not provided? I actually had that in my repo and used a
> slightly older patch here, but I'm not sure if its okay to strongly
> couple an ndctl release to a kernel version.

I was thinking that too. Typically we don't guarantee ndctl to work with
old kernels, but this does seem like a bit of an invasive change.

Dan, thoughts?
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  reply	other threads:[~2018-06-26 16:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 15:37 [PATCH 0/2] Namespace creation fixups Keith Busch
2018-06-26 15:37 ` [PATCH 1/2] libnvdimm: Use largest contiguous area for namespace size Keith Busch
2018-07-05 17:57   ` Dan Williams
2018-07-05 17:58     ` Keith Busch
2018-06-26 15:37 ` [PATCH] ndctl: Use max_available_extent for creating namespaces Keith Busch
2018-06-26 16:19   ` Verma, Vishal L
2018-06-26 16:29     ` Keith Busch
2018-06-26 16:27       ` Verma, Vishal L [this message]
2018-06-26 16:32         ` Dan Williams
2018-06-26 16:34           ` Verma, Vishal L
2018-06-26 15:37 ` [PATCH 2/2] libnvdimm: Export max available extent Keith Busch

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=1530030454.27147.23.camel@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=keith.busch@intel.com \
    --cc=linux-nvdimm@lists.01.org \
    --cc=y-goto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.