From: Huaisheng Ye <yehs2007@zoho.com>
To: snitzer@redhat.com, agk@redhat.com
Cc: dan.j.williams@intel.com, hch@lst.de, jack@suse.cz,
corbet@lwn.net, dm-devel@redhat.com,
linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org,
linux-doc@vger.kernel.org, chengnt@lenovo.com,
Huaisheng Ye <yehs1@lenovo.com>
Subject: [RFC PATCH v2 2/4] dm-writecache: get rid of memory_data flush to writecache_flush_entry
Date: Wed, 9 Jan 2019 13:31:25 +0800 [thread overview]
Message-ID: <20190109053127.8128-3-yehs2007@zoho.com> (raw)
In-Reply-To: <20190109053127.8128-1-yehs2007@zoho.com>
From: Huaisheng Ye <yehs1@lenovo.com>
writecache_flush_region only works when SSD mode.
If wc->pmem_mode sets, writecache_flush_region doesn't need to be called in
writecache_flush_entry.
Signed-off-by: Huaisheng Ye <yehs1@lenovo.com>
---
drivers/md/dm-writecache.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/md/dm-writecache.c b/drivers/md/dm-writecache.c
index 2d8e0c0..c69317c 100644
--- a/drivers/md/dm-writecache.c
+++ b/drivers/md/dm-writecache.c
@@ -688,8 +688,6 @@ static void writecache_poison_lists(struct dm_writecache *wc)
static void writecache_flush_entry(struct dm_writecache *wc, struct wc_entry *e)
{
writecache_flush_region(wc, memory_entry(wc, e));
- if (WC_MODE_PMEM(wc))
- writecache_flush_region(wc, memory_data(wc, e));
}
static bool writecache_entry_is_committed(struct dm_writecache *wc, struct wc_entry *e)
--
1.8.3.1
next prev parent reply other threads:[~2019-01-09 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 5:31 [RFC PATCH v2 0/4] add parameter for pmem cache device init Huaisheng Ye
2019-01-09 5:31 ` [RFC PATCH v2 1/4] dm-writecache: remove unused size to writecache_flush_region Huaisheng Ye
2019-01-09 5:31 ` Huaisheng Ye [this message]
2019-01-09 5:31 ` [RFC PATCH v2 3/4] dm-writecache: expand pmem_reinit for struct dm_writecache Huaisheng Ye
2019-01-09 5:31 ` [RFC PATCH v2 4/4] Documentation/device-mapper: add optional parameter reinit Huaisheng Ye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190109053127.8128-3-yehs2007@zoho.com \
--to=yehs2007@zoho.com \
--cc=agk@redhat.com \
--cc=chengnt@lenovo.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=snitzer@redhat.com \
--cc=yehs1@lenovo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).