On Fri, Jun 8, 2018 at 3:20 PM Adam Ford wrote:
>
> On Fri, Jun 8, 2018 at 2:15 PM Tom Rini wrote:
> >
> > On Fri, Jun 08, 2018 at 10:30:36AM -0500, Adam Ford wrote:
> > > On Tue, May 22, 2018 at 11:24 AM Tom Rini wrote:
> > > >
> > > > When dealing with filesystems that come from block devices
On Fri, Jun 8, 2018 at 2:15 PM Tom Rini wrote:
>
> On Fri, Jun 08, 2018 at 10:30:36AM -0500, Adam Ford wrote:
> > On Tue, May 22, 2018 at 11:24 AM Tom Rini wrote:
> > >
> > > When dealing with filesystems that come from block devices we can get a
> > > noticeable performance gain in some use
On Fri, Jun 08, 2018 at 10:30:36AM -0500, Adam Ford wrote:
> On Tue, May 22, 2018 at 11:24 AM Tom Rini wrote:
> >
> > When dealing with filesystems that come from block devices we can get a
> > noticeable performance gain in some use cases from having the block
> > cache enabled. The code paths
On Tue, May 22, 2018 at 11:24 AM Tom Rini wrote:
>
> When dealing with filesystems that come from block devices we can get a
> noticeable performance gain in some use cases from having the block
> cache enabled. The code paths are valid in other cases when we have BLK
> set and may provide wins
On Tue, May 22, 2018 at 12:24:16PM -0400, Tom Rini wrote:
> When dealing with filesystems that come from block devices we can get a
> noticeable performance gain in some use cases from having the block
> cache enabled. The code paths are valid in other cases when we have BLK
> set and may
When dealing with filesystems that come from block devices we can get a
noticeable performance gain in some use cases from having the block
cache enabled. The code paths are valid in other cases when we have BLK
set and may provide wins in raw reads in some use cases, so have this be
default when
6 matches
Mail list logo
