avid, This patch reduces xfs_bmap_btalloc() stack usage by 50 bytes by moving part of its body into a helper function. This results in some variables not taking stack space in xfs_bmap_btalloc()
ike a very good approach, it pushes a lot of large local vars off into the helper. There is one build-time problem if DEBUG is turned on: if (args.fsbno != NULLFSBLOCK) { ap->firstblock = ap->
seless wrapper that doesn't help making the code more readable. Signed-off-by: Christoph Hellwig <hch@xxxxxx> Index: linux-2.6-xfs/fs/xfs/xfs_mount.c == -- linux-2.6-xfs.orig/fs/xfs/xfs_mount.
Benjamin, David, struct kiocb is placed on stack by, for example, do_sync_write(). Eventually it contributes to xfs writeout path's stack usage, among others. This is *the* path which causes 4
u please attach your patches inline, Denys (see Documentation/SubmittingPatches)? I have a set of patches that introduces new functionality into the allocator (dynamic allocation policies) that
ou who asked for patches. It's not like I decided to nag you because I have nothing better to do. Actually, my plate is pretty full with other things already. So I went ahead and actually spend
e re-based my freeze patches from linux-2.6.25-rc7 to linux-2.6.25. There is no functional change from the previous version. The patch-set consists of the following three patches. [PATCH 1/3] I
his patch reduces xfs_bmap_btalloc() stack usage by 50 bytes by moving part of its body into a helper function. This results in some variables not taking stack space in xfs_bmap_btalloc()
ed, 23 Apr 2008 21:48:53 -0400 vous écriviez: You may greatly enhance performance on hardware RAID by using the "nobarrier" mount option. However in this case you must have proper power and/or