From: Jan Kara <jack@suse.cz>
To: Michal Hocko <mhocko@suse.com>
Cc: Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.cz>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Dave Jiang <dave.jiang@intel.com>,
akpm@linux-foundation.org, linux-nvdimm@lists.01.org, hch@lst.de,
linux-mm@kvack.org, tytso@mit.edu, dan.j.williams@intel.com
Subject: Re: [PATCH v4 1/3] dax: masking off __GFP_FS in fs DAX handlers
Date: Wed, 21 Dec 2016 13:36:03 +0100 [thread overview]
Message-ID: <20161221123603.GA10320@quack2.suse.cz> (raw)
In-Reply-To: <20161220101352.GE3769@dhcp22.suse.cz>
On Tue 20-12-16 11:13:52, Michal Hocko wrote:
> I am not fully familiar with the DAX changes which started this
> discussion but if there is a reclaim recursion problem from within the
> fault path then the scope api sounds like a good fit here.
>
> [1] http://lkml.kernel.org/r/20161215140715.12732-1-mhocko@kernel.org
Yes, once your scope API and associated ext4 changes are in, we can stop
playing tricks with gfp_mask in DAX code at least for ext4.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-12-21 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 23:40 [PATCH v4 1/3] dax: masking off __GFP_FS in fs DAX handlers Dave Jiang
2016-12-15 23:40 ` [PATCH v4 2/3] mm, dax: make pmd_fault() and friends to be the same as fault() Dave Jiang
2016-12-15 23:40 ` [PATCH v4 3/3] mm, dax: move pmd_fault() to take only vmf parameter Dave Jiang
2016-12-19 17:41 ` Jan Kara
2016-12-16 1:07 ` [PATCH v4 1/3] dax: masking off __GFP_FS in fs DAX handlers Dave Chinner
2016-12-16 16:19 ` Ross Zwisler
2016-12-16 22:04 ` Dave Chinner
2016-12-19 17:56 ` Jiang, Dave
2016-12-19 19:53 ` Jan Kara
2016-12-19 21:17 ` Dave Chinner
2016-12-20 10:13 ` Michal Hocko
2016-12-21 12:36 ` Jan Kara [this message]
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=20161221123603.GA10320@quack2.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mhocko@suse.com \
--cc=ross.zwisler@linux.intel.com \
--cc=tytso@mit.edu \
/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).