Re: [PATCH] bcache: writeback rate shouldn't artifically clamp

Stefan-- On Sun, Oct 8, 2017 at 12:50 AM, Stefan Priebe - Profihost AG wrote: > Is there a branch with all patches available? I have a github repository up of linux-next, with commits currently being staged for next on top, at https://github.com/mlyle/linux/ . The

Re: [PATCH] bcache: writeback rate shouldn't artifically clamp

On 2017/10/8 下午3:50, Stefan Priebe - Profihost AG wrote: > Is there a branch with all patches available? > > Stefan Hi Stefan, Current I just organize patch files not a git tree branch. The reason is, I send bcache patches by emails to Jens and Cc linux-bcache and linux-block, in order to make

Re: [PATCH] bcache: writeback rate shouldn't artifically clamp

On 2017/10/8 下午1:25, Michael Lyle wrote: > The previous code artificially limited writeback rate to 100 > blocks/second (NSEC_PER_MSEC), which is a rate that can be met on fast > hardware. The rate limiting code works fine (though with decreased > precision) up to 3 orders of magnitude

[PATCH] bcache: writeback rate shouldn't artifically clamp

The previous code artificially limited writeback rate to 100 blocks/second (NSEC_PER_MSEC), which is a rate that can be met on fast hardware. The rate limiting code works fine (though with decreased precision) up to 3 orders of magnitude faster, so use NSEC_PER_SEC. Additionally, ensure that