Re: [PATCH v2] writeback: mark sysctl vm.block_dump for removal

2013-01-15 Thread Fengguang Wu
On Wed, Jan 16, 2013 at 03:07:53AM +0100, Jan Kara wrote: > On Tue 15-01-13 08:28:13, Tejun Heo wrote: > > vm.block_dump is nasty in that it dumps IO traces directly to printk. > > It isn't scalable and can easily lead to looping behavior - IO > > generating kernel message which in turn genreates l

Re: [PATCH v2] writeback: mark sysctl vm.block_dump for removal

2013-01-15 Thread Jan Kara
On Tue 15-01-13 08:28:13, Tejun Heo wrote: > vm.block_dump is nasty in that it dumps IO traces directly to printk. > It isn't scalable and can easily lead to looping behavior - IO > generating kernel message which in turn genreates log IO, ad > infinitum. > > Now that proper tracepoints are in pla