Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+vfs\:\s+reduce\s+stack\s+usage\s+in\s+write_cache

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+vfs\:\s+reduce\s+stack\s+usage\s+in\s+write_cache_pages\s*$/: 3 ]

Total 3 documents matching your query.

1. stack usage in xfs_page_state_convert() (score: 1): Author: Denys Vlasenko <vda.linux@xxxxxxxxxxxxxx>; Date: Sun, 27 Apr 2008 04:24:10 +0200; cularly liked it. But the inlining of functions with -funit-at-a-time was such a problem for the s; /archives/xfs/2008-04/msg00478.html (8,915 bytes)
2. xfs_bmap_btalloc() (score: 1): Author: Denys Vlasenko <vda.linux@xxxxxxxxxxxxxx>; Date: Sun, 27 Apr 2008 04:24:10 +0200; date already is completely Linux specific due to the VFS flags passed in, so it might aswell be merged into xfs_fs_remount. Signed-off-by: Christoph Hellwig <hch@xxxxxx> Index: linux-2.6-xfs; /archives/xfs/2008-04/msg01074.html (8,915 bytes)
3. [PATCH] vfs: reduce stack usage in write_cache_pages() (score: 1): Author: Denys Vlasenko <vda.linux@xxxxxxxxxxxxxx>; Date: Sun, 27 Apr 2008 04:24:10 +0200; Hi Al, David, vfs function write_cache_pages() appears on the xfs writeout path. It's *the* path which causes 4k stack overflows on i386 with xfs. This function uses ~100 bytes of stack on 32-bit i38; /archives/xfs/2008-04/msg01670.html (8,915 bytes)

Current List: 1 - 3
Page: [1]