From: Dan Williams <dan.j.williams@intel.com>
To: Jane Chu <jane.chu@oracle.com>
Cc: "nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>,
Ira Weiny <ira.weiny@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] dax: Kill DEV_DAX_PMEM_COMPAT
Date: Fri, 29 Oct 2021 18:44:46 -0700 [thread overview]
Message-ID: <CAPcyv4j-6tEOZg8pW_pfuftdqqFReD29e-fG0vu=GSP7YxbF2Q@mail.gmail.com> (raw)
In-Reply-To: <53eaa74c-0cfb-a333-4e57-8f59949b91e9@oracle.com>
On Fri, Oct 29, 2021 at 5:19 PM Jane Chu <jane.chu@oracle.com> wrote:
>
> Hi, Dan,
>
> I think we're still using _COMPAT, but likely don't need to.
Ugh, really? I hope not, that would be unfortunate. Perhaps are you
using libndctl / libdaxctl rather than going to /sys/class/dax
directly? Those have shipped backwards compatibility for a while now,
so applications using those libraries should not notice the switch to
the /sys/bus/dax ABI. The only other open source application I could
find that had /sys/class/dax dependencies was fio, but I fixed that up
years ago as well.
> What is your patch based on?
This is based on a branch I have with Christoph's recent dax reworks.
I have a test merge of that pushed out on my libnvdimm-pending branch
if you want to give it a try.
https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git/log/?h=libnvdimm-pending
next prev parent reply other threads:[~2021-10-30 1:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 15:45 Dan Williams
2021-10-28 15:57 ` Dave Hansen
2021-10-30 0:19 ` Jane Chu
2021-10-30 1:44 ` Dan Williams [this message]
2021-10-30 3:54 ` Jane Chu
2021-11-15 21:20 ` [PATCH v2] " Dan Williams
2021-11-23 19:11 ` Jane Chu
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='CAPcyv4j-6tEOZg8pW_pfuftdqqFReD29e-fG0vu=GSP7YxbF2Q@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=jane.chu@oracle.com \
--cc=linux-mm@kvack.org \
--cc=nvdimm@lists.linux.dev \
--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