Re: [PATCH v2 2/2] smartpqi: limit transfer length to 1MB

Don, > The smartpqi firmware will bypass the cache for any request larger > than 1MB, so we should cap the request size to avoid any > performance degradation in kernels later than v4.3 Ping on these... -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH v2 2/2] smartpqi: limit transfer length to 1MB

Don, > The smartpqi firmware will bypass the cache for any request larger > than 1MB, so we should cap the request size to avoid any > performance degradation in kernels later than v4.3 Ping on these... -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH v2 2/2] smartpqi: limit transfer length to 1MB

On Fri, Jun 23, 2017 at 05:40:06PM +0800, Yadan Fan wrote: > The smartpqi firmware will bypass the cache for any request larger > than 1MB, so we should cap the request size to avoid any > performance degradation in kernels later than v4.3 > > This degradation is caused from

Re: [PATCH v2 2/2] smartpqi: limit transfer length to 1MB

On Fri, Jun 23, 2017 at 05:40:06PM +0800, Yadan Fan wrote: > The smartpqi firmware will bypass the cache for any request larger > than 1MB, so we should cap the request size to avoid any > performance degradation in kernels later than v4.3 > > This degradation is caused from

[PATCH v2 2/2] smartpqi: limit transfer length to 1MB

The smartpqi firmware will bypass the cache for any request larger than 1MB, so we should cap the request size to avoid any performance degradation in kernels later than v4.3 This degradation is caused from d2be537c3ba3568acd79cd178327b842e60d035e, which changed max_sectors_kb to 1280k, but the

[PATCH v2 2/2] smartpqi: limit transfer length to 1MB

The smartpqi firmware will bypass the cache for any request larger than 1MB, so we should cap the request size to avoid any performance degradation in kernels later than v4.3 This degradation is caused from d2be537c3ba3568acd79cd178327b842e60d035e, which changed max_sectors_kb to 1280k, but the