Re: [Resend] Possible bug in __fragmentation_index()

2018-02-09 Thread Robert Harris
On 2 Feb 2018, at 17:47, Mel Gorman wrote: > On Fri, Feb 02, 2018 at 02:16:39PM +, Robert Harris wrote: >> I was planning to annotate the opaque calculation in >> __fragmentation_index() but on closer inspection I think there may be a >> bug. I could use some feedback. A belated thank you

Re: [Resend] Possible bug in __fragmentation_index()

2018-02-09 Thread Robert Harris
On 2 Feb 2018, at 17:47, Mel Gorman wrote: > On Fri, Feb 02, 2018 at 02:16:39PM +, Robert Harris wrote: >> I was planning to annotate the opaque calculation in >> __fragmentation_index() but on closer inspection I think there may be a >> bug. I could use some feedback. A belated thank you

Re: [Resend] Possible bug in __fragmentation_index()

2018-02-02 Thread Mel Gorman
On Fri, Feb 02, 2018 at 02:16:39PM +, Robert Harris wrote: > I was planning to annotate the opaque calculation in > __fragmentation_index() but on closer inspection I think there may be a > bug. I could use some feedback. > > Firstly, for the case of fragmentation and ignoring the scaling, >

Re: [Resend] Possible bug in __fragmentation_index()

2018-02-02 Thread Mel Gorman
On Fri, Feb 02, 2018 at 02:16:39PM +, Robert Harris wrote: > I was planning to annotate the opaque calculation in > __fragmentation_index() but on closer inspection I think there may be a > bug. I could use some feedback. > > Firstly, for the case of fragmentation and ignoring the scaling, >

[Resend] Possible bug in __fragmentation_index()

2018-02-02 Thread Robert Harris
I was planning to annotate the opaque calculation in __fragmentation_index() but on closer inspection I think there may be a bug. I could use some feedback. Firstly, for the case of fragmentation and ignoring the scaling, __fragmentation_index() purports to return a value in the range 0 to 1.

[Resend] Possible bug in __fragmentation_index()

2018-02-02 Thread Robert Harris
I was planning to annotate the opaque calculation in __fragmentation_index() but on closer inspection I think there may be a bug. I could use some feedback. Firstly, for the case of fragmentation and ignoring the scaling, __fragmentation_index() purports to return a value in the range 0 to 1.