From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Jan Kara <jack@suse.cz>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-nvdimm@ml01.01.org,
Andrew Morton <akpm@linux-foundation.org>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH 01/21] mm: Join struct fault_env and vm_fault
Date: Wed, 16 Nov 2016 14:13:01 +0300 [thread overview]
Message-ID: <20161116111301.GA27027@node.shutemov.name> (raw)
In-Reply-To: <20161116105132.GR3142@twins.programming.kicks-ass.net>
On Wed, Nov 16, 2016 at 11:51:32AM +0100, Peter Zijlstra wrote:
> On Wed, Nov 16, 2016 at 12:50:21AM +0300, Kirill A. Shutemov wrote:
> > On Fri, Nov 04, 2016 at 05:24:57AM +0100, Jan Kara wrote:
> > > Currently we have two different structures for passing fault information
> > > around - struct vm_fault and struct fault_env. DAX will need more
> > > information in struct vm_fault to handle its faults so the content of
> > > that structure would become event closer to fault_env. Furthermore it
> > > would need to generate struct fault_env to be able to call some of the
> > > generic functions. So at this point I don't think there's much use in
> > > keeping these two structures separate. Just embed into struct vm_fault
> > > all that is needed to use it for both purposes.
> > >
> > > Signed-off-by: Jan Kara <jack@suse.cz>
> >
> > I'm not necessary dislike this, but I remember Peter had objections before
> > when I proposed something similar.
> >
> > Peter?
>
> My objection was that it would be a layering violation. The 'filesystem'
> shouldn't know about page-tables, all it should do is return a page
> matching a specific offset.
Well, this layering violation is already there (blame me): see
vm_ops->map_pages(). :P
> So fault_env manages the core vm parts and has the page-table bits in,
> vm_fault manages the filesystem interface and gets us a page given an
> offset.
>
> Now, I'm entirely out of touch wrt DAX, so I've not idea what that
> needs/wants.
I think we are better off with one structure. It streamlines code in quite
a few places.
--
Kirill A. Shutemov
--
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>
next prev parent reply other threads:[~2016-11-16 11:13 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 4:24 [PATCH 0/21 v4 RESEND] dax: Clear dirty bits after flushing caches Jan Kara
2016-11-04 4:24 ` [PATCH 01/21] mm: Join struct fault_env and vm_fault Jan Kara
2016-11-15 21:50 ` Kirill A. Shutemov
2016-11-16 10:51 ` Peter Zijlstra
2016-11-16 11:01 ` Jan Kara
2016-11-16 17:21 ` Peter Zijlstra
2016-11-17 9:07 ` Jan Kara
2016-11-16 11:13 ` Kirill A. Shutemov [this message]
2016-11-04 4:24 ` [PATCH 02/21] mm: Use vmf->address instead of of vmf->virtual_address Jan Kara
2016-11-15 21:55 ` Kirill A. Shutemov
2016-11-16 11:05 ` Jan Kara
2016-11-16 11:32 ` Kirill A. Shutemov
2016-11-16 11:55 ` Jan Kara
2016-11-04 4:24 ` [PATCH 03/21] mm: Use pgoff in struct vm_fault instead of passing it separately Jan Kara
2016-11-15 22:01 ` Kirill A. Shutemov
2016-11-04 4:25 ` [PATCH 04/21] mm: Use passed vm_fault structure in __do_fault() Jan Kara
2016-11-15 22:05 ` Kirill A. Shutemov
2016-11-04 4:25 ` [PATCH 05/21] mm: Trim __do_fault() arguments Jan Kara
2016-11-15 22:10 ` Kirill A. Shutemov
2016-11-16 13:12 ` Jan Kara
2016-11-04 4:25 ` [PATCH 06/21] mm: Use passed vm_fault structure for in wp_pfn_shared() Jan Kara
2016-11-15 22:10 ` Kirill A. Shutemov
2016-11-04 4:25 ` [PATCH 07/21] mm: Add orig_pte field into vm_fault Jan Kara
2016-11-15 22:14 ` Kirill A. Shutemov
2016-11-16 20:00 ` Ross Zwisler
2016-11-04 4:25 ` [PATCH 08/21] mm: Allow full handling of COW faults in ->fault handlers Jan Kara
2016-11-15 22:20 ` Kirill A. Shutemov
2016-11-04 4:25 ` [PATCH 09/21] mm: Factor out functionality to finish page faults Jan Kara
2016-11-15 22:21 ` Kirill A. Shutemov
2016-11-04 4:25 ` [PATCH 10/21] mm: Move handling of COW faults into DAX code Jan Kara
2016-11-15 22:22 ` Kirill A. Shutemov
2016-11-16 21:28 ` Ross Zwisler
2016-11-17 9:36 ` Jan Kara
2016-11-04 4:25 ` [PATCH 11/21] mm: Remove unnecessary vma->vm_ops check Jan Kara
2016-11-15 22:28 ` Kirill A. Shutemov
2016-11-16 13:29 ` Jan Kara
2016-11-16 14:27 ` Kirill A. Shutemov
2016-11-16 14:43 ` Jan Kara
2016-11-04 4:25 ` [PATCH 12/21] mm: Factor out common parts of write fault handling Jan Kara
2016-11-15 22:30 ` Kirill A. Shutemov
2016-11-04 4:25 ` [PATCH 13/21] mm: Pass vm_fault structure into do_page_mkwrite() Jan Kara
2016-11-15 22:40 ` Kirill A. Shutemov
2016-11-16 13:34 ` Jan Kara
2016-11-04 4:25 ` [PATCH 14/21] mm: Use vmf->page during WP faults Jan Kara
2016-11-15 22:42 ` Kirill A. Shutemov
2016-11-04 4:25 ` [PATCH 15/21] mm: Move part of wp_page_reuse() into the single call site Jan Kara
2016-11-15 22:44 ` Kirill A. Shutemov
2016-11-04 4:25 ` [PATCH 16/21] mm: Provide helper for finishing mkwrite faults Jan Kara
2016-11-15 22:52 ` Kirill A. Shutemov
2016-11-16 13:39 ` Jan Kara
2016-11-04 4:25 ` [PATCH 17/21] mm: Change return values of finish_mkwrite_fault() Jan Kara
2016-11-15 22:57 ` Kirill A. Shutemov
2016-11-04 4:25 ` [PATCH 18/21] mm: Export follow_pte() Jan Kara
2016-11-04 4:25 ` [PATCH 19/21] dax: Make cache flushing protected by entry lock Jan Kara
2016-11-04 4:25 ` [PATCH 20/21] dax: Protect PTE modification on WP fault by radix tree " Jan Kara
2016-11-04 4:25 ` [PATCH 21/21] dax: Clear dirty entry tags on cache flush Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2016-11-01 22:36 [PATCH 0/21 v4] dax: Clear dirty bits after flushing caches Jan Kara
2016-11-01 22:36 ` [PATCH 01/21] mm: Join struct fault_env and vm_fault Jan Kara
2016-11-02 9:58 ` Kirill A. Shutemov
2016-11-04 4:32 ` Jan Kara
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=20161116111301.GA27027@node.shutemov.name \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=peterz@infradead.org \
--cc=ross.zwisler@linux.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