From: Jan Kara <jack@suse.cz>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Christoph Hellwig" <hch@lst.de>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
"Martin Schwidefsky" <schwidefsky@de.ibm.com>,
"Heiko Carstens" <heiko.carstens@de.ibm.com>,
"Michal Hocko" <mhocko@suse.com>,
"kbuild test robot" <lkp@intel.com>,
"Thomas Meyer" <thomas@m3y3r.de>,
"Dave Jiang" <dave.jiang@intel.com>,
"Jérôme Glisse" <jglisse@redhat.com>, "Jan Kara" <jack@suse.cz>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"Linux MM" <linux-mm@kvack.org>,
"Gerald Schaefer" <gerald.schaefer@de.ibm.com>
Subject: Re: [PATCH v10] mm: introduce MEMORY_DEVICE_FS_DAX and CONFIG_DEV_PAGEMAP_OPS
Date: Mon, 21 May 2018 11:04:10 +0200 [thread overview]
Message-ID: <20180521090410.7ygosxzjfhceqrq4@quack2.suse.cz> (raw)
In-Reply-To: <CAPcyv4iO1yss0sfBzHVDy3qja_wc+JT2Zi1zwtApDckTeuG2wQ@mail.gmail.com>
On Fri 18-05-18 09:00:29, Dan Williams wrote:
> On Fri, May 18, 2018 at 2:46 AM, Christoph Hellwig <hch@lst.de> wrote:
> >> + select DEV_PAGEMAP_OPS if (ZONE_DEVICE && !FS_DAX_LIMITED)
> >
> > Btw, what was the reason again we couldn't get rid of FS_DAX_LIMITED?
>
> The last I heard from Gerald they were still mildly interested in
> keeping the dccssblk dax support going with this limited mode, and
> threatened to add full page support at a later date:
>
> ---
> From: Gerald
>
> dcssblk seems to work fine, I did not see any SIGBUS while "executing
> in place" from dcssblk with the current upstream kernel, maybe because
> we only use dcssblk with fs dax in read-only mode.
>
> Anyway, the dcssblk change is fine with me. I will look into adding
> struct pages for dcssblk memory later, to make it work again with
> this change, but for now I do not know of anyone needing this in the
> upstream kernel.
>
> https://www.spinics.net/lists/linux-xfs/msg14628.html
> ---
We definitely do have customers using "execute in place" on s390x from
dcssblk. I've got about two bug reports for it when customers were updating
from old kernels using original XIP to kernels using DAX. So we need to
keep that working.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2018-05-21 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 20:06 [PATCH v10] mm: introduce MEMORY_DEVICE_FS_DAX and CONFIG_DEV_PAGEMAP_OPS Dan Williams
2018-05-18 9:00 ` Jan Kara
2018-05-18 9:46 ` Christoph Hellwig
2018-05-18 16:00 ` Dan Williams
2018-05-21 9:04 ` Jan Kara [this message]
2018-05-22 6:28 ` Christoph Hellwig
2018-05-23 18:50 ` Gerald Schaefer
2018-05-29 20:26 ` Dan Williams
2018-06-01 15:01 ` Gerald Schaefer
2018-06-02 0:03 ` 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=20180521090410.7ygosxzjfhceqrq4@quack2.suse.cz \
--to=jack@suse.cz \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=jglisse@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=lkp@intel.com \
--cc=mhocko@suse.com \
--cc=schwidefsky@de.ibm.com \
--cc=thomas@m3y3r.de \
/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).