From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm@lists.01.org
Subject: Re: [ndctl PATCH 1/2] ndctl: provide a method to invalidate the bus list
Date: Thu, 24 Mar 2016 10:04:52 -0600 [thread overview]
Message-ID: <20160324160452.GA5725@linux.intel.com> (raw)
In-Reply-To: <20160324011653.20651.27454.stgit@dwillia2-desk3.jf.intel.com>
On Wed, Mar 23, 2016 at 06:16:53PM -0700, Dan Williams wrote:
> Consider the following scenario:
>
> ndctl_new()
> ndctl_bus_foreach()
> <install a new nvdimm-bus provider>
> ndctl_bus_foreach()
>
> ...the second ndctl_bus_foreach() will not see any new buses because the
> bus results are cached. When the holder of the context knows that it
> has invalidated the bus list it needs to call ndctl_invalidate() so that
> subsequent ndctl_bus_foreach() scans are guaranteed to see new buses.
>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> lib/libndctl.c | 22 ++++++++++++++++++----
> lib/libndctl.sym | 1 +
> lib/ndctl/libndctl.h.in | 1 +
I can't get this patch to apply because I don't have lib/ndctl/libndctl.h.in
in my source tree.
I'm using your upstream repo:
https://github.com/pmem/ndctl.git
and AFAICT this file doesn't exist in any upstream branches.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2016-03-24 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 1:16 [ndctl PATCH 0/2] fix the nfit_test fallback for 'ndctl bat' Dan Williams
2016-03-24 1:16 ` [ndctl PATCH 1/2] ndctl: provide a method to invalidate the bus list Dan Williams
2016-03-24 16:04 ` Ross Zwisler [this message]
2016-03-24 16:15 ` Dan Williams
2016-03-24 1:16 ` [ndctl PATCH 2/2] ndctl: don't skip bat tests if nfit_test not available 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=20160324160452.GA5725@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=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 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.