From: Dan Williams <dan.j.williams@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Linux NVDIMM <nvdimm@lists.linux.dev>,
linux-s390 <linux-s390@vger.kernel.org>,
Gerald Schaefer <gerald.schaefer@de.ibm.com>,
Joao Martins <joao.m.martins@oracle.com>
Subject: Re: can we finally kill off CONFIG_FS_DAX_LIMITED
Date: Fri, 20 Aug 2021 08:41:52 -0700 [thread overview]
Message-ID: <CAPcyv4i5GHUXPCEu4RbD1x_=usTdK2VWqHfvHFEHijDYBg+CLw@mail.gmail.com> (raw)
In-Reply-To: <20210820054340.GA28560@lst.de>
[ add Gerald and Joao ]
On Thu, Aug 19, 2021 at 10:44 PM Christoph Hellwig <hch@lst.de> wrote:
>
> Hi all,
>
> looking at the recent ZONE_DEVICE related changes we still have a
> horrible maze of different code paths. I already suggested to
> depend on ARCH_HAS_PTE_SPECIAL for ZONE_DEVICE there, which all modern
> architectures have anyway. But the other odd special case is
> CONFIG_FS_DAX_LIMITED which is just used for the xpram driver. Does
> this driver still see use? If so can we make it behave like the
> other DAX drivers and require a pgmap? I think the biggest missing
> part would be to implement ARCH_HAS_PTE_DEVMAP for s390.
>
Gerald,
Might you still be looking to help dcssblk get out of FS_DAX_LIMITED
jail [1]? I recall Martin saying that 'struct page' overhead was
prohibitive. I don't know if Joao's 'struct page' diet patches could
help alleviate that at all (would require the filesystem to only
allocate blocks in large page sizes).
[1]: https://lore.kernel.org/r/20180523205017.0f2bc83e@thinkpad
next prev parent reply other threads:[~2021-08-20 15:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 5:43 can we finally kill off CONFIG_FS_DAX_LIMITED Christoph Hellwig
2021-08-20 15:41 ` Dan Williams [this message]
2021-08-20 17:42 ` Dan Williams
2021-08-20 19:03 ` Gerald Schaefer
2021-08-24 14:17 ` Joao Martins
2021-08-23 14:05 ` Gerald Schaefer
2021-08-23 19:47 ` Gerald Schaefer
2021-08-23 20:21 ` Dan Williams
2021-08-24 14:09 ` Joao Martins
2021-08-24 14:53 ` Dan Williams
2021-08-24 18:24 ` Gerald Schaefer
2021-08-24 18:44 ` Dan Williams
2021-10-14 23:04 ` Jason Gunthorpe
2021-10-15 0:22 ` Joao Martins
2021-10-18 23:30 ` Jason Gunthorpe
2021-10-19 4:26 ` Dan Williams
2021-10-19 14:20 ` Jason Gunthorpe
2021-10-19 15:20 ` Joao Martins
2021-10-19 15:38 ` Felix Kuehling
2021-10-19 17:38 ` Dan Williams
2021-10-19 17:54 ` Jason Gunthorpe
2021-08-24 6:49 ` David Hildenbrand
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='CAPcyv4i5GHUXPCEu4RbD1x_=usTdK2VWqHfvHFEHijDYBg+CLw@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=borntraeger@de.ibm.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=joao.m.martins@oracle.com \
--cc=linux-s390@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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).