forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
mm: merge populate and nopage into fault (fixes nonlinear)
Nonlinear mappings are (AFAIKS) simply a virtual memory concept that encodes the virtual address -> file offset differently from linear mappings. ->populate is a layering violation because the filesystem/pagecache code should need to know anything about the virtual memory mapping. The hitch here is that the ->nopage handler didn't pass down enough information (ie. pgoff). But it is more logical to pass pgoff rather than have the ->nopage function calculate it itself anyway (because that's a similar layering violation). Having the populate handler install the pte itself is likewise a nasty thing to be doing. This patch introduces a new fault handler that replaces ->nopage and ->populate and (later) ->nopfn. Most of the old mechanism is still in place so there is a lot of duplication and nice cleanups that can be removed if everyone switches over. The rationale for doing this in the first place is that nonlinear mappings are subject to the pagefault vs invalidate/truncate race too, and it seemed stupid to duplicate the synchronisation logic rather than just consolidate the two. After this patch, MAP_NONBLOCK no longer sets up ptes for pages present in pagecache. Seems like a fringe functionality anyway. NOPAGE_REFAULT is removed. This should be implemented with ->fault, and no users have hit mainline yet. [[email protected]: cleanup] [[email protected]: doc. fixes for readahead] [[email protected]: build fix] Signed-off-by: Nick Piggin <[email protected]> Signed-off-by: Randy Dunlap <[email protected]> Cc: Mark Fasheh <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
- Loading branch information
Nick Piggin
authored and
Linus Torvalds
committed
Jul 19, 2007
1 parent
d00806b
commit 54cb882
Showing
20 changed files
with
394 additions
and
272 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -135,6 +135,33 @@ Who: Greg Kroah-Hartman <[email protected]> | |
|
||
--------------------------- | ||
|
||
What: filemap_nopage, filemap_populate | ||
When: April 2007 | ||
Why: These legacy interfaces no longer have any callers in the kernel and | ||
any functionality provided can be provided with filemap_fault. The | ||
removal schedule is short because they are a big maintainence burden | ||
and have some bugs. | ||
Who: Nick Piggin <[email protected]> | ||
|
||
--------------------------- | ||
|
||
What: vm_ops.populate, install_page | ||
When: April 2007 | ||
Why: These legacy interfaces no longer have any callers in the kernel and | ||
any functionality provided can be provided with vm_ops.fault. | ||
Who: Nick Piggin <[email protected]> | ||
|
||
--------------------------- | ||
|
||
What: vm_ops.nopage | ||
When: February 2008, provided in-kernel callers have been converted | ||
Why: This interface is replaced by vm_ops.fault, but it has been around | ||
forever, is used by a lot of drivers, and doesn't cost much to | ||
maintain. | ||
Who: Nick Piggin <[email protected]> | ||
|
||
--------------------------- | ||
|
||
What: Interrupt only SA_* flags | ||
When: September 2007 | ||
Why: The interrupt related SA_* flags are replaced by IRQF_* to move them | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.