Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
linux
Commits
dadf196c
Commit
dadf196c
authored
Nov 06, 2002
by
Russell Cattelan
Committed by
Nathan Scott
Nov 06, 2002
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[XFS] narrow down comment
SGI Modid: 2.5.x-xfs:slinx:131504a
parent
980eab8d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
15 deletions
+12
-15
fs/xfs/linux/xfs_aops.c
fs/xfs/linux/xfs_aops.c
+12
-15
No files found.
fs/xfs/linux/xfs_aops.c
View file @
dadf196c
...
...
@@ -350,25 +350,22 @@ cluster_write(
/*
* Calling this without startio set means we are being asked to make a dirty
* page ready for freeing it's buffers. When called with startio set then
* we are coming from writepage.
* we are coming from writepage.
*
* When called with startio e.g. from write page it is important that we write WHOLE page if
* possible. The bh->b_state's can not know of any of the blocks or which block for that matter
* are dirty due to map writes, and therefore bh uptodate is only vaild if the page
* itself isn't completely uptodate. Some layers may clear the page dirty flag prior to
* calling write page under the assumption the entire page will be written out, by not writing
* out the whole page the page can be reused before all vaild dirty data is written out.
* Note: in the case of a page that has been dirty'd by mapwrite and but partially setup by
* block_prepare_write the bh->b_states's will not agree and only ones setup by BPW/BCW will have
* When called with startio e.g. from
* write page it is important that we write WHOLE page if possible. The
* bh->b_state's can not know of any of the blocks or which block for
* that matter are dirty due to map writes, and therefore bh uptodate is
* only vaild if the pagei itself isn't completely uptodate. Some layers
* may clear the page dirty flag prior to calling write page under the
* assumption the entire page will be written out, by not writing out the
* whole page the page can be reused before all vaild dirty data is
* written out. Note: in the case of a page that has been dirty'd by
* mapwrite and but partially setup by block_prepare_write the
* bh->b_states's will not agree and only ones setup by BPW/BCW will have
* valid state, thus the whole page must be written out thing.
*/
STATIC
int
delalloc_convert
(
struct
page
*
page
,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment