[+cc from "Enable use of Solid State Hybrid Drives"
https://lkml.org/lkml/2014/10/29/698 ]
On Thu, 28 Jul 2016, Martin K. Petersen wrote:
> > "Eric" == Eric Wheeler writes:
> Eric> [...] This may imply that
> Eric> we need a new way to flag cache bypass
[+cc from "Enable use of Solid State Hybrid Drives"
https://lkml.org/lkml/2014/10/29/698 ]
On Thu, 28 Jul 2016, Martin K. Petersen wrote:
> > "Eric" == Eric Wheeler writes:
> Eric> [...] This may imply that
> Eric> we need a new way to flag cache bypass from userspace [...]
> Eric>
> "Eric" == Eric Wheeler writes:
Eric,
Eric> However, just because FADV_SEQUENTIAL is flagged doesn't mean the
Eric> cache should bypass. Filesystems can fragment, and while the file
Eric> being read may be read sequentially, the blocks on which it
Eric> resides
> "Eric" == Eric Wheeler writes:
Eric,
Eric> However, just because FADV_SEQUENTIAL is flagged doesn't mean the
Eric> cache should bypass. Filesystems can fragment, and while the file
Eric> being read may be read sequentially, the blocks on which it
Eric> resides may not be. Same thing for
On 29/07/16 01:50, Eric Wheeler wrote:
> Hello all,
>
> With the many SSD caching layers being developed (bcache, dm-cache,
> dm-writeboost, etc), how could we flag a bio from userspace to indicate
> whether the bio is preferred to hit spinning disks instead of an SSD?
>
> Unnecessary
On 29/07/16 01:50, Eric Wheeler wrote:
> Hello all,
>
> With the many SSD caching layers being developed (bcache, dm-cache,
> dm-writeboost, etc), how could we flag a bio from userspace to indicate
> whether the bio is preferred to hit spinning disks instead of an SSD?
>
> Unnecessary
6 matches
Mail list logo