- 1. set_buffer_dirty_uptodate (score: 1)
- Author: Marcelo Tosatti <marcelo@xxxxxxxxxxxxxxxx>
- Date: Sun, 17 Dec 2000 23:34:25 -0200 (BRST)
- I was looking at the pagebuf code while I noted that set_buffer_dirty_uptodate (pagebuf/page_buf_io.c:1188) may sleep waiting for bdflush to clean some dirty buffers because it calls balance_dirty()
- /archives/xfs/2000-12/msg00158.html (8,419 bytes)
- 2. Re: set_buffer_dirty_uptodate (score: 1)
- Author: Russell Cattelan <cattelan@xxxxxxxxxxx>
- Date: Tue, 19 Dec 2000 18:16:31 -0600
- Sorry I haven't gotten back to you... I haven't had a chance to look this over, but yes this might be a problem. Have you been able to demonstrate this problem? -- Russell Cattelan cattelan@xxxxxxxxx
- /archives/xfs/2000-12/msg00171.html (9,480 bytes)
- 3. Re: set_buffer_dirty_uptodate (score: 1)
- Author: Marcelo Tosatti <marcelo@xxxxxxxxxxxxxxxx>
- Date: Tue, 19 Dec 2000 20:27:39 -0200 (BRST)
- No problem. Nope. I was just reading XFS code and noticed the potential problem. Dont you people have lockmeter output's of filesystem benchmarks on the 32p o2k? That may give us a hint.
- /archives/xfs/2000-12/msg00172.html (10,087 bytes)
- 4. Re: set_buffer_dirty_uptodate (score: 1)
- Author: Rajagopal Ananthanarayanan <ananth@xxxxxxx>
- Date: Tue, 26 Dec 2000 14:20:48 -0800
- [ just getting back to mail after a vacation ] Indeed this is a problem; the patch I've been sending out pushes the balance_dirty call after all xfs locks have been dropped. If you haven't seen the p
- /archives/xfs/2000-12/msg00194.html (10,677 bytes)
- 5. Re: set_buffer_dirty_uptodate (score: 1)
- Author: Marcelo Tosatti <marcelo@xxxxxxxxxxxxxxxx>
- Date: Tue, 26 Dec 2000 19:41:09 -0200 (BRST)
- <snip> The correct solution to your problem is to not pass __GFP_IO in the allocation flag passed to __alloc_pages. This way the allocation routines will not try to do any kind of IO and will not wai
- /archives/xfs/2000-12/msg00195.html (10,317 bytes)
- 6. set_buffer_dirty_uptodate (score: 1)
- Author: Marcelo Tosatti <marcelo@xxxxxxxxxxxxxxxx>
- Date: Sun, 17 Dec 2000 23:34:25 -0200 (BRST)
- I was looking at the pagebuf code while I noted that set_buffer_dirty_uptodate (pagebuf/page_buf_io.c:1188) may sleep waiting for bdflush to clean some dirty buffers because it calls balance_dirty()
- /archives/xfs/2000-12/msg00373.html (8,419 bytes)
- 7. Re: set_buffer_dirty_uptodate (score: 1)
- Author: Russell Cattelan <cattelan@xxxxxxxxxxx>
- Date: Tue, 19 Dec 2000 18:16:31 -0600
- Sorry I haven't gotten back to you... I haven't had a chance to look this over, but yes this might be a problem. Have you been able to demonstrate this problem? -- Russell Cattelan cattelan@xxxxxxxxx
- /archives/xfs/2000-12/msg00386.html (9,480 bytes)
- 8. Re: set_buffer_dirty_uptodate (score: 1)
- Author: Marcelo Tosatti <marcelo@xxxxxxxxxxxxxxxx>
- Date: Tue, 19 Dec 2000 20:27:39 -0200 (BRST)
- No problem. Nope. I was just reading XFS code and noticed the potential problem. Dont you people have lockmeter output's of filesystem benchmarks on the 32p o2k? That may give us a hint.
- /archives/xfs/2000-12/msg00387.html (10,087 bytes)
- 9. Re: set_buffer_dirty_uptodate (score: 1)
- Author: Rajagopal Ananthanarayanan <ananth@xxxxxxx>
- Date: Tue, 26 Dec 2000 14:20:48 -0800
- [ just getting back to mail after a vacation ] Indeed this is a problem; the patch I've been sending out pushes the balance_dirty call after all xfs locks have been dropped. If you haven't seen the p
- /archives/xfs/2000-12/msg00409.html (10,677 bytes)
- 10. Re: set_buffer_dirty_uptodate (score: 1)
- Author: Marcelo Tosatti <marcelo@xxxxxxxxxxxxxxxx>
- Date: Tue, 26 Dec 2000 19:41:09 -0200 (BRST)
- <snip> The correct solution to your problem is to not pass __GFP_IO in the allocation flag passed to __alloc_pages. This way the allocation routines will not try to do any kind of IO and will not wai
- /archives/xfs/2000-12/msg00410.html (10,317 bytes)
This search system is powered by
Namazu