From: "Chenjie (K)" <chenjie6@huawei.com>
To: Matthew Wilcox <willy@linux.intel.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
<linux-fsdevel@vger.kernel.org>, <zhihui.gao@huawei.com>,
<linux-kernel@vger.kernel.org>, <lizefan@huawei.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] bugfix dax fault page should be no cache
Date: Wed, 13 Jan 2016 11:47:12 +0800 [thread overview]
Message-ID: <5695C8C0.1080005@huawei.com> (raw)
In-Reply-To: <20160112125131.GB8945@linux.intel.com>
The DAX means Direct Access for files,if the pages have cache,
the file is not direct access. But in normal condition,
we can not find the problem directly.
In our case, we use ext2 filesystem with dax on the reserved mem.
we mmap the file and write some things ,the file is not changed immediately.
this is the wrong place to change that attribute:
Do you mean
add
ext4_file_mmap/ext2_file_mmap
if (IS_DAX(file_inode(file))) {
vma->vm_ops = &ext4_dax_vm_ops;
vma->vm_flags |= VM_MIXEDMAP;
+ vma->vm_page_prot = pgprot_writecombine(vma->vm_page_prot);
} else {
like this ???
On 2016/1/12 20:51, Matthew Wilcox wrote:
> On Tue, Jan 12, 2016 at 07:43:45PM +0800, chenjie6@huawei.com wrote:
>> From: chenjie <chenjie6@huawei.com>
>>
>> We show the pte:
>> *pte=01600000159c8fd3
>> The page should be no_cache attr,it will be better.
>
> I disagree. What data do you have to show that the WC attribute would
> be better than WB?
>
> Even if we agree to that, this is the wrong place to change that
> attribute, so the patch is NAKed. But you need more than "it will
> be better".
>
> .
>
next prev parent reply other threads:[~2016-01-13 3:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 11:43 [PATCH] bugfix dax fault page should be no cache chenjie6
2016-01-12 12:51 ` Matthew Wilcox
2016-01-13 3:47 ` Chenjie (K) [this message]
2016-01-13 16:32 ` Matthew Wilcox
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=5695C8C0.1080005@huawei.com \
--to=chenjie6@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.com \
--cc=zhihui.gao@huawei.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;
as well as URLs for NNTP newsgroup(s).