Re: [PATCH v3] xfs: introduce object readahead to log recovery

2013-08-14 Thread Dave Chinner
On Wed, Aug 14, 2013 at 01:59:02PM +0800, Zhi Yong Wu wrote: > On Wed, Aug 14, 2013 at 1:35 PM, Dave Chinner wrote: > > On Wed, Jul 31, 2013 at 04:42:45PM +0800, zwu.ker...@gmail.com wrote: > >> From: Zhi Yong Wu > >> > >> It can take a long time to run log recovery operation because it is >

Re: [PATCH v3] xfs: introduce object readahead to log recovery

2013-08-14 Thread Dave Chinner
On Wed, Aug 14, 2013 at 01:59:02PM +0800, Zhi Yong Wu wrote: On Wed, Aug 14, 2013 at 1:35 PM, Dave Chinner da...@fromorbit.com wrote: On Wed, Jul 31, 2013 at 04:42:45PM +0800, zwu.ker...@gmail.com wrote: From: Zhi Yong Wu wu...@linux.vnet.ibm.com It can take a long time to run log

Re: [PATCH v3] xfs: introduce object readahead to log recovery

2013-08-13 Thread Zhi Yong Wu
On Wed, Aug 14, 2013 at 1:35 PM, Dave Chinner wrote: > On Wed, Jul 31, 2013 at 04:42:45PM +0800, zwu.ker...@gmail.com wrote: >> From: Zhi Yong Wu >> >> It can take a long time to run log recovery operation because it is >> single threaded and is bound by read latency. We can find that it took

Re: [PATCH v3] xfs: introduce object readahead to log recovery

2013-08-13 Thread Dave Chinner
On Wed, Jul 31, 2013 at 04:42:45PM +0800, zwu.ker...@gmail.com wrote: > From: Zhi Yong Wu > > It can take a long time to run log recovery operation because it is > single threaded and is bound by read latency. We can find that it took > most of the time to wait for the read IO to occur, so if

Re: [PATCH v3] xfs: introduce object readahead to log recovery

2013-08-13 Thread Dave Chinner
On Wed, Jul 31, 2013 at 04:42:45PM +0800, zwu.ker...@gmail.com wrote: From: Zhi Yong Wu wu...@linux.vnet.ibm.com It can take a long time to run log recovery operation because it is single threaded and is bound by read latency. We can find that it took most of the time to wait for the read

Re: [PATCH v3] xfs: introduce object readahead to log recovery

2013-08-13 Thread Zhi Yong Wu
On Wed, Aug 14, 2013 at 1:35 PM, Dave Chinner da...@fromorbit.com wrote: On Wed, Jul 31, 2013 at 04:42:45PM +0800, zwu.ker...@gmail.com wrote: From: Zhi Yong Wu wu...@linux.vnet.ibm.com It can take a long time to run log recovery operation because it is single threaded and is bound by read

Re: [PATCH v3] xfs: introduce object readahead to log recovery

2013-08-07 Thread Zhi Yong Wu
HI, xfs maintainers, any comments? On Wed, Jul 31, 2013 at 4:42 PM, wrote: > From: Zhi Yong Wu > > It can take a long time to run log recovery operation because it is > single threaded and is bound by read latency. We can find that it took > most of the time to wait for the read IO to

Re: [PATCH v3] xfs: introduce object readahead to log recovery

2013-08-07 Thread Zhi Yong Wu
HI, xfs maintainers, any comments? On Wed, Jul 31, 2013 at 4:42 PM, zwu.ker...@gmail.com wrote: From: Zhi Yong Wu wu...@linux.vnet.ibm.com It can take a long time to run log recovery operation because it is single threaded and is bound by read latency. We can find that it took most of

[PATCH v3] xfs: introduce object readahead to log recovery

2013-07-31 Thread zwu . kernel
From: Zhi Yong Wu It can take a long time to run log recovery operation because it is single threaded and is bound by read latency. We can find that it took most of the time to wait for the read IO to occur, so if one object readahead is introduced to log recovery, it will obviously reduce the

[PATCH v3] xfs: introduce object readahead to log recovery

2013-07-31 Thread zwu . kernel
From: Zhi Yong Wu wu...@linux.vnet.ibm.com It can take a long time to run log recovery operation because it is single threaded and is bound by read latency. We can find that it took most of the time to wait for the read IO to occur, so if one object readahead is introduced to log recovery, it