On Fri, Jan 09, 2015 at 10:57:10AM +, Mel Gorman wrote:
> On Thu, Jan 08, 2015 at 09:46:27AM +0100, Vlastimil Babka wrote:
> > On 01/08/2015 09:18 AM, Joonsoo Kim wrote:
> > > On Tue, Jan 06, 2015 at 10:05:39AM +0100, Vlastimil Babka wrote:
> > >> On 12/03/2014 08:52 AM, Joonsoo Kim wrote:
> >
On Fri, Jan 09, 2015 at 10:57:10AM +, Mel Gorman wrote:
On Thu, Jan 08, 2015 at 09:46:27AM +0100, Vlastimil Babka wrote:
On 01/08/2015 09:18 AM, Joonsoo Kim wrote:
On Tue, Jan 06, 2015 at 10:05:39AM +0100, Vlastimil Babka wrote:
On 12/03/2014 08:52 AM, Joonsoo Kim wrote:
It'd be
On Thu, Jan 08, 2015 at 09:46:27AM +0100, Vlastimil Babka wrote:
> On 01/08/2015 09:18 AM, Joonsoo Kim wrote:
> > On Tue, Jan 06, 2015 at 10:05:39AM +0100, Vlastimil Babka wrote:
> >> On 12/03/2014 08:52 AM, Joonsoo Kim wrote:
> >> > It'd be useful to know where the both scanner is start. And, it
On Thu, Jan 08, 2015 at 09:46:27AM +0100, Vlastimil Babka wrote:
On 01/08/2015 09:18 AM, Joonsoo Kim wrote:
On Tue, Jan 06, 2015 at 10:05:39AM +0100, Vlastimil Babka wrote:
On 12/03/2014 08:52 AM, Joonsoo Kim wrote:
It'd be useful to know where the both scanner is start. And, it also be
On Thu, Jan 08, 2015 at 09:46:27AM +0100, Vlastimil Babka wrote:
> On 01/08/2015 09:18 AM, Joonsoo Kim wrote:
> > On Tue, Jan 06, 2015 at 10:05:39AM +0100, Vlastimil Babka wrote:
> >> On 12/03/2014 08:52 AM, Joonsoo Kim wrote:
> >> > It'd be useful to know where the both scanner is start. And, it
On 01/08/2015 09:18 AM, Joonsoo Kim wrote:
> On Tue, Jan 06, 2015 at 10:05:39AM +0100, Vlastimil Babka wrote:
>> On 12/03/2014 08:52 AM, Joonsoo Kim wrote:
>> > It'd be useful to know where the both scanner is start. And, it also be
>> > useful to know current range where compaction work. It will
On Tue, Jan 06, 2015 at 10:05:39AM +0100, Vlastimil Babka wrote:
> On 12/03/2014 08:52 AM, Joonsoo Kim wrote:
> > It'd be useful to know where the both scanner is start. And, it also be
> > useful to know current range where compaction work. It will help to find
> > odd behaviour or problem on
On Thu, Jan 08, 2015 at 09:46:27AM +0100, Vlastimil Babka wrote:
On 01/08/2015 09:18 AM, Joonsoo Kim wrote:
On Tue, Jan 06, 2015 at 10:05:39AM +0100, Vlastimil Babka wrote:
On 12/03/2014 08:52 AM, Joonsoo Kim wrote:
It'd be useful to know where the both scanner is start. And, it also be
On Tue, Jan 06, 2015 at 10:05:39AM +0100, Vlastimil Babka wrote:
On 12/03/2014 08:52 AM, Joonsoo Kim wrote:
It'd be useful to know where the both scanner is start. And, it also be
useful to know current range where compaction work. It will help to find
odd behaviour or problem on
On 01/08/2015 09:18 AM, Joonsoo Kim wrote:
On Tue, Jan 06, 2015 at 10:05:39AM +0100, Vlastimil Babka wrote:
On 12/03/2014 08:52 AM, Joonsoo Kim wrote:
It'd be useful to know where the both scanner is start. And, it also be
useful to know current range where compaction work. It will help to
On 12/03/2014 08:52 AM, Joonsoo Kim wrote:
> It'd be useful to know where the both scanner is start. And, it also be
> useful to know current range where compaction work. It will help to find
> odd behaviour or problem on compaction.
Overall it looks good, just two questions:
1) Why change the
On 12/03/2014 08:52 AM, Joonsoo Kim wrote:
It'd be useful to know where the both scanner is start. And, it also be
useful to know current range where compaction work. It will help to find
odd behaviour or problem on compaction.
Overall it looks good, just two questions:
1) Why change the pfn
On 01/05/2015 03:33 AM, Joonsoo Kim wrote:
> On Wed, Dec 03, 2014 at 04:52:05PM +0900, Joonsoo Kim wrote:
>> It'd be useful to know where the both scanner is start. And, it also be
>> useful to know current range where compaction work. It will help to find
>> odd behaviour or problem on
On 01/05/2015 03:33 AM, Joonsoo Kim wrote:
On Wed, Dec 03, 2014 at 04:52:05PM +0900, Joonsoo Kim wrote:
It'd be useful to know where the both scanner is start. And, it also be
useful to know current range where compaction work. It will help to find
odd behaviour or problem on compaction.
On Wed, Dec 03, 2014 at 04:52:05PM +0900, Joonsoo Kim wrote:
> It'd be useful to know where the both scanner is start. And, it also be
> useful to know current range where compaction work. It will help to find
> odd behaviour or problem on compaction.
>
> Signed-off-by: Joonsoo Kim
Hello,
On Wed, Dec 03, 2014 at 04:52:05PM +0900, Joonsoo Kim wrote:
It'd be useful to know where the both scanner is start. And, it also be
useful to know current range where compaction work. It will help to find
odd behaviour or problem on compaction.
Signed-off-by: Joonsoo Kim
It'd be useful to know where the both scanner is start. And, it also be
useful to know current range where compaction work. It will help to find
odd behaviour or problem on compaction.
Signed-off-by: Joonsoo Kim
---
include/linux/compaction.h|2 +
include/trace/events/compaction.h |
It'd be useful to know where the both scanner is start. And, it also be
useful to know current range where compaction work. It will help to find
odd behaviour or problem on compaction.
Signed-off-by: Joonsoo Kim iamjoonsoo@lge.com
---
include/linux/compaction.h|2 +
18 matches
Mail list logo
