Re: undefined shift in wb_update_dirty_ratelimit()

On Mon, Dec 7, 2015 at 4:26 PM, Tejun Heo wrote: > Hello, Andrey. > On Mon, Dec 07, 2015 at 05:17:06PM +0300, Andrey Ryabinin wrote: >> I've hit undefined shift in wb_update_dirty_ratelimit() which does some >> mysterious 'step' calculations: >> >> /* >

Re: undefined shift in wb_update_dirty_ratelimit()

On Mon, Dec 7, 2015 at 4:26 PM, Tejun Heo <t...@kernel.org> wrote: > Hello, Andrey. > On Mon, Dec 07, 2015 at 05:17:06PM +0300, Andrey Ryabinin wrote: >> I've hit undefined shift in wb_update_dirty_ratelimit() which does some >> mysterious 'step' calculations: >>

Re: undefined shift in wb_update_dirty_ratelimit()

Hello, Andrey. On Mon, Dec 07, 2015 at 05:17:06PM +0300, Andrey Ryabinin wrote: > I've hit undefined shift in wb_update_dirty_ratelimit() which does some > mysterious 'step' calculations: > > /* >* Don't pursue 100% rate matching. It's impossible since the balanced

undefined shift in wb_update_dirty_ratelimit()

I've hit undefined shift in wb_update_dirty_ratelimit() which does some mysterious 'step' calculations: /* * Don't pursue 100% rate matching. It's impossible since the balanced * rate itself is constantly fluctuating. So decrease the track speed * when it gets

undefined shift in wb_update_dirty_ratelimit()

I've hit undefined shift in wb_update_dirty_ratelimit() which does some mysterious 'step' calculations: /* * Don't pursue 100% rate matching. It's impossible since the balanced * rate itself is constantly fluctuating. So decrease the track speed * when it gets

Re: undefined shift in wb_update_dirty_ratelimit()

Hello, Andrey. On Mon, Dec 07, 2015 at 05:17:06PM +0300, Andrey Ryabinin wrote: > I've hit undefined shift in wb_update_dirty_ratelimit() which does some > mysterious 'step' calculations: > > /* >* Don't pursue 100% rate matching. It's impossible since the balanced