Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[patch\s+20\/22\]\s+move\s+vn_iowait\s+\/\s+vn_iowake\s+into\s+xfs

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[patch\s+20\/22\]\s+move\s+vn_iowait\s+\/\s+vn_iowake\s+into\s+xfs_aops\.c\s*$/: 12 ]

Total 12 documents matching your query.

1. [patch 20/22] move vn_iowait / vn_iowake into xfs_aops.c (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 02 Dec 2008 11:04:50 -0500; The whole machinery to wait on I/O completion is related to the I/O path and should be there instead of in xfs_vnode.c. Also give the functions more descriptive names. Signed-off-by: Christoph Hellwi; /archives/xfs/2008-12/msg00041.html (17,881 bytes)
2. Re: [patch 20/22] move vn_iowait / vn_iowake into xfs_aops.c (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Wed, 3 Dec 2008 14:17:19 +1100; I'm not sure that "xfs_ioend_..." is the best name - it looks slightly weird in some of the callers' contexts. Just dropping the "end" out of the names makes the code read much better (i.e. xfs_io_wa; /archives/xfs/2008-12/msg00081.html (11,100 bytes)
3. Re: [patch 20/22] move vn_iowait / vn_iowake into xfs_aops.c (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 3 Dec 2008 05:58:31 -0500; xfs_ioend_* wasn't my first choice either. I first did xfs_iowait/xfs_iowake, but that clashes with the buffercache. And having names just different by an underscore doesn't seem good either. Any oth; /archives/xfs/2008-12/msg00096.html (11,207 bytes)
4. Re: [patch 20/22] move vn_iowait / vn_iowake into xfs_aops.c (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 4 Dec 2008 08:48:09 +1100; Ah, so it does. but: Perhaps we should kill that define and just use xfs_buf_iowait(bp) because it documents that we really are waiting on a specific object.... Then maybe we can use xfs_data_iowake/; /archives/xfs/2008-12/msg00109.html (12,270 bytes)
5. [patch 20/22] move vn_iowait / vn_iowake into xfs_aops.c (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 02 Dec 2008 11:04:50 -0500; /archives/xfs/2008-12/msg00658.html (17,881 bytes)
6. Re: [patch 20/22] move vn_iowait / vn_iowake into xfs_aops.c (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Wed, 3 Dec 2008 14:17:19 +1100; /archives/xfs/2008-12/msg00698.html (11,100 bytes)
7. Re: [patch 20/22] move vn_iowait / vn_iowake into xfs_aops.c (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 3 Dec 2008 05:58:31 -0500; /archives/xfs/2008-12/msg00713.html (11,207 bytes)
8. Re: [patch 20/22] move vn_iowait / vn_iowake into xfs_aops.c (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 4 Dec 2008 08:48:09 +1100; /archives/xfs/2008-12/msg00726.html (12,270 bytes)
9. [patch 20/22] move vn_iowait / vn_iowake into xfs_aops.c (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 02 Dec 2008 11:04:50 -0500; The whole machinery to wait on I/O completion is related to the I/O path and should be there instead of in xfs_vnode.c. Also give the functions more descriptive names. Signed-off-by: Christoph Hellwi; /archives/xfs/2008-12/msg01275.html (17,913 bytes)
10. Re: [patch 20/22] move vn_iowait / vn_iowake into xfs_aops.c (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Wed, 3 Dec 2008 14:17:19 +1100; I'm not sure that "xfs_ioend_..." is the best name - it looks slightly weird in some of the callers' contexts. Just dropping the "end" out of the names makes the code read much better (i.e. xfs_io_wa; /archives/xfs/2008-12/msg01315.html (11,196 bytes)
11. Re: [patch 20/22] move vn_iowait / vn_iowake into xfs_aops.c (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 3 Dec 2008 05:58:31 -0500; xfs_ioend_* wasn't my first choice either. I first did xfs_iowait/xfs_iowake, but that clashes with the buffercache. And having names just different by an underscore doesn't seem good either. Any oth; /archives/xfs/2008-12/msg01330.html (11,387 bytes)
12. Re: [patch 20/22] move vn_iowait / vn_iowake into xfs_aops.c (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 4 Dec 2008 08:48:09 +1100; Ah, so it does. but: Perhaps we should kill that define and just use xfs_buf_iowait(bp) because it documents that we really are waiting on a specific object.... Then maybe we can use xfs_data_iowake/; /archives/xfs/2008-12/msg01343.html (12,452 bytes)

Current List: 1 - 12
Page: [1]