Re: can't get bache's sequential_cutoff to work

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 25.07.2013 02:14, schrieb Kent Overstreet:
> On Tue, Jul 23, 2013 at 10:38:49PM +0200, Stefan Priebe wrote:
>> Mhm works directly on block device but not with XFS on top.
> 
> That's odd...
> 
> Do you suppose you could look at what blktrace says is going down? If
> you could compare what blktrace says is going to the bcache device with
> and without XFS, hopefully that'll show what's going wrong...
> 
> Only thing I can think of that would cause it is for some reason XFS is
> sending bios down in the wrong order... which normally wouldn't be _too_
> painful since both the elevator and the disk's cache will reorder the
> IOs, so I can see how that would slip by.
Hi,

will try to have a look. But can it also be that the history of 128
entries is too small under my workload and bcache does not detect the
sequence? Is there a way to try with a higher value like 1024?

Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM Kernel]     [Linux Filesystem Development]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux