On 07/18/2012 07:57 PM, David Sterba wrote: > On Mon, Jul 16, 2012 at 02:05:25PM -0400, Liu Bo wrote: >> v2->v3: adopt kernel native pagevec instead of kmalloc. > > Do we really use the pagevec features here? It looks more like a fancy > way to employ a simple array ... > > And with a simple array we could use 16 page pointers covering 16 * 4k = > 64k bytes which looks more friendly than 14 * 4K = 56K (available in a > pagevec). This may have a negative effect on the troughput, but I > haven't measured that. Can you please benchmark it against pagevec? > Thanks for the advice. Yes, it is a simple array that is needed. Indeed I even tried 128 page array, with which I can get the biggest improvement on my box. Basically in range [1, 128], the more pages in the array, the bigger improvement we'll get. But as Chris suggested, my test is really a race case in practical use, half of improvement is somehow enough, so we turn to use pagevec struct because it is closer to how we solve similar problems in other parts of the kernel. thanks, liubo > > david > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
