From: Jeff Moyer <jmoyer@redhat.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "linux-nvdimm\@lists.01.org" <linux-nvdimm@ml01.01.org>,
Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>,
Linux ACPI <linux-acpi@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] libnvdimm, region: sysfs trigger for nvdimm_flush()
Date: Thu, 27 Apr 2017 15:43:41 -0400 [thread overview]
Message-ID: <x491ssdprf6.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <CAPcyv4hDmwSO8szjn+mqL6xpW2H92WsTDn=8qLtJi7Y8kduX5Q@mail.gmail.com> (Dan Williams's message of "Thu, 27 Apr 2017 12:21:54 -0700")
Dan Williams <dan.j.williams@intel.com> writes:
> We also still seem to need a discovery mechanism as I've had questions
> about "how do I tell if my system supports deep flush?". That's where
> sysfs is much better than an ioctl. The need for deep flush discovery
> tips the scales, at least for me, to also do deep flush triggering
> through the same interface.
Return ENXIO or EOPNOTSUPP from the ioctl when it isn't supported?
Cheers,
Jeff
next prev parent reply other threads:[~2017-04-27 19:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 23:49 [PATCH v2 0/2] libnvdimm: export wpq flush interface Dan Williams
2017-04-24 23:49 ` [PATCH v2 1/2] libnvdimm, region: fix flush hint detection crash Dan Williams
2017-04-26 19:43 ` Jeff Moyer
2017-04-26 20:04 ` Dan Williams
2017-04-24 23:50 ` [PATCH v2 2/2] libnvdimm, region: sysfs trigger for nvdimm_flush() Dan Williams
2017-04-25 16:37 ` Ross Zwisler
2017-04-25 16:38 ` Dan Williams
2017-04-25 20:17 ` [PATCH v3] " Dan Williams
2017-04-26 20:38 ` Jeff Moyer
2017-04-26 23:00 ` Dan Williams
2017-04-27 13:45 ` Jeff Moyer
2017-04-27 16:56 ` Dan Williams
2017-04-27 18:41 ` Jeff Moyer
2017-04-27 19:17 ` Dan Williams
2017-04-27 19:21 ` Dan Williams
2017-04-27 19:43 ` Jeff Moyer [this message]
2017-04-27 19:40 ` Jeff Moyer
2017-04-27 20:02 ` Dan Williams
2017-04-27 21:36 ` Dan Williams
2017-04-26 23:36 ` [PATCH v4] " Dan Williams
2017-04-27 22:17 ` [PATCH v5] " 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=x491ssdprf6.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=m.mizuma@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