All of lore.kernel.org
 help / color / mirror / Atom feed
* dm-cache as a writeback cache that streams all writes to cache, and then updates origin
@ 2016-07-23  1:56 Gary
  2016-07-25 14:03 ` Edward Thornber
  0 siblings, 1 reply; 2+ messages in thread
From: Gary @ 2016-07-23  1:56 UTC (permalink / raw)
  To: dm-devel


[-- Attachment #1.1: Type: text/plain, Size: 1343 bytes --]

I haven't tested the MQ policy since I'm on kernel 4.6, I am on SMQ. I have
a spinning disk as the origin that is falling behind as a mysql slave. I
added an ssd writeback cache but I can still see a a large amount of random
writes going to the spinning disk on iotop. The filesystem is XFS. Origin
is 2tb, but the dataset I am working with is only 305gb. The cache is 40gb
total.

dmsetup status shows

cached: 0 3906766976 cache 8 330/1663 512 163686/163686 1781562 5956880
6792625 24895886 18847 18847 3398 1 writeback 2 migration_threshold 2048
smq 0 rw -

a minute later shows

cached: 0 3906766976 cache 8 330/1663 512 163686/163686 1781956 5959500
6794474 24908493 18850 18850 3396 1 writeback 2 migration_threshold 2048
smq 0 rw -

I was looking over the archives of dm-cache and came across
https://www.redhat.com/archives/dm-devel/2015-September/msg00090.html

I understand that dm-cache does not just blindly stream all writes to the
cache and then update the origin. Is there some way I can enable that
though (even if it involves changing code)? The hotspot feature is
impractical for this workload and is of little help it seems. I know the
SSD taking writes by itself can keep up, I just can't dedicate that much
SSD space to this right now. I have to turn barriers off to make the hard
disk keep up and I'd rather not do that.

[-- Attachment #1.2: Type: text/html, Size: 1636 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: dm-cache as a writeback cache that streams all writes to cache, and then updates origin
  2016-07-23  1:56 dm-cache as a writeback cache that streams all writes to cache, and then updates origin Gary
@ 2016-07-25 14:03 ` Edward Thornber
  0 siblings, 0 replies; 2+ messages in thread
From: Edward Thornber @ 2016-07-25 14:03 UTC (permalink / raw)
  To: Gary; +Cc: dm-devel

On Fri, Jul 22, 2016 at 06:56:47PM -0700, Gary wrote:
> I understand that dm-cache does not just blindly stream all writes to the
> cache and then update the origin. Is there some way I can enable that
> though (even if it involves changing code)? 

No, sorry.  I really wish I'd called it dm-hotspot.

- Joe

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-07-25 14:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-07-23  1:56 dm-cache as a writeback cache that streams all writes to cache, and then updates origin Gary
2016-07-25 14:03 ` Edward Thornber

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.