[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190131022955.9920-1-yehs2007@zoho.com>
Date: Thu, 31 Jan 2019 10:29:50 +0800
From: Huaisheng Ye <yehs2007@...o.com>
To: mpatocka@...hat.com, snitzer@...hat.com, agk@...hat.com
Cc: dan.j.williams@...el.com, hch@....de, jack@...e.cz, corbet@....net,
dm-devel@...hat.com, linux-kernel@...r.kernel.org,
linux-nvdimm@...ts.01.org, linux-doc@...r.kernel.org,
Huaisheng Ye <yehs1@...ovo.com>
Subject: [PATCH v3 0/5] Optimize writecache when using pmem as cache
From: Huaisheng Ye <yehs1@...ovo.com>
This patch set could be used for dm-writecache when use persistent
memory as cache data device.
Patch 1 and 2 go towards removing unused parameter and codes which
actually doesn't really work.
Patch 3 and 4 are targeted at solving problem fn ctr failed to work
due to invalid magic or version, which is caused by the super block
of pmem has messy data stored.
Patch 5 is used for getting the status of seq_count.
Changes Since v2:
- seq_count is important for flush operations, output it within status
for debugging and analyzing code behavior.
[1]: https://lkml.org/lkml/2019/1/3/43
[2]: https://lkml.org/lkml/2019/1/9/6
Huaisheng Ye (5):
dm-writecache: remove unused size to writecache_flush_region
dm-writecache: get rid of memory_data flush to writecache_flush_entry
dm-writecache: expand pmem_reinit for struct dm_writecache
Documentation/device-mapper: add optional parameter reinit
dm-writecache: output seq_count within status
Documentation/device-mapper/writecache.txt | 4 ++++
drivers/md/dm-writecache.c | 23 +++++++++++++----------
2 files changed, 17 insertions(+), 10 deletions(-)
--
1.8.3.1
Powered by blists - more mailing lists