From: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
To: nvdimm@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: dan.j.williams@intel.com, jmoyer@redhat.com, david@redhat.com,
mst@redhat.com, cohuck@redhat.com, vishal.l.verma@intel.com,
dave.jiang@intel.com, ira.weiny@intel.com,
pankaj.gupta.linux@gmail.com,
Pankaj Gupta <pankaj.gupta@ionos.com>
Subject: [RFC v2 0/2] virtio-pmem: Asynchronous flush
Date: Mon, 26 Jul 2021 08:08:53 +0200 [thread overview]
Message-ID: <20210726060855.108250-1-pankaj.gupta.linux@gmail.com> (raw)
From: Pankaj Gupta <pankaj.gupta@ionos.com>
Jeff reported preflush order issue with the existing implementation
of virtio pmem preflush. Dan suggested[1] to implement asynchronous flush
for virtio pmem using work queue as done in md/RAID. This patch series
intends to solve the preflush ordering issue and also makes the flush
asynchronous for the submitting thread.
Submitting this patch series for review. Sorry, It took me long time to
come back to this due to some personal reasons.
RFC v1 -> RFC v2
- More testing and bug fix.
[1] https://marc.info/?l=linux-kernel&m=157446316409937&w=2
Pankaj Gupta (2):
virtio-pmem: Async virtio-pmem flush
pmem: enable pmem_submit_bio for asynchronous flush
drivers/nvdimm/nd_virtio.c | 72 ++++++++++++++++++++++++++++--------
drivers/nvdimm/pmem.c | 17 ++++++---
drivers/nvdimm/virtio_pmem.c | 10 ++++-
drivers/nvdimm/virtio_pmem.h | 14 +++++++
4 files changed, 91 insertions(+), 22 deletions(-)
--
2.25.1
next reply other threads:[~2021-07-26 6:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 6:08 Pankaj Gupta [this message]
2021-07-26 6:08 ` [RFC v2 1/2] virtio-pmem: Async virtio-pmem flush Pankaj Gupta
2021-08-25 17:25 ` Dan Williams
2021-08-25 20:01 ` Pankaj Gupta
2021-08-25 21:50 ` Dan Williams
2021-08-25 22:00 ` Pankaj Gupta
2021-08-25 22:08 ` Dan Williams
2021-08-27 12:39 ` Pankaj Gupta
2021-07-26 6:08 ` [RFC v2 2/2] pmem: Enable pmem_submit_bio for asynchronous flush Pankaj Gupta
2021-08-19 11:08 ` [RFC v2 0/2] virtio-pmem: Asynchronous flush Pankaj Gupta
2021-10-16 8:23 ` Pankaj Gupta
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=20210726060855.108250-1-pankaj.gupta.linux@gmail.com \
--to=pankaj.gupta.linux@gmail.com \
--cc=cohuck@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@redhat.com \
--cc=ira.weiny@intel.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nvdimm@lists.linux.dev \
--cc=pankaj.gupta@ionos.com \
--cc=vishal.l.verma@intel.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).