From: David Hildenbrand <david@redhat.com>
To: Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org
Cc: dan.j.williams@intel.com, vishal.l.verma@intel.com,
dave.jiang@intel.com, mst@redhat.com, jmoyer@redhat.com,
pankaj.gupta@cloud.ionos.com
Subject: Re: [RFC 0/2] virtio-pmem: Asynchronous flush
Date: Thu, 11 Mar 2021 17:31:40 +0100 [thread overview]
Message-ID: <7e55abc4-5c91-efb8-1b32-87570dde62cc@redhat.com> (raw)
In-Reply-To: <20200420131947.41991-1-pankaj.gupta.linux@gmail.com>
On 20.04.20 15:19, Pankaj Gupta wrote:
> 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 from the submitting thread POV.
>
> Submitting this patch series for feeback and is in WIP. I have
> done basic testing and currently doing more testing.
>
> Pankaj Gupta (2):
> pmem: make nvdimm_flush asynchronous
> virtio_pmem: Async virtio-pmem flush
>
> drivers/nvdimm/nd_virtio.c | 66 ++++++++++++++++++++++++++----------
> drivers/nvdimm/pmem.c | 15 ++++----
> drivers/nvdimm/region_devs.c | 3 +-
> drivers/nvdimm/virtio_pmem.c | 9 +++++
> drivers/nvdimm/virtio_pmem.h | 12 +++++++
> 5 files changed, 78 insertions(+), 27 deletions(-)
>
> [1] https://marc.info/?l=linux-kernel&m=157446316409937&w=2
>
Just wondering, was there any follow up of this or are we still waiting
for feedback? :)
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-03-11 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 13:19 Pankaj Gupta
2020-04-20 13:19 ` [RFC 1/2] pmem: make nvdimm_flush asynchronous Pankaj Gupta
2020-04-20 13:19 ` [RFC 2/2] virtio_pmem: Async virtio-pmem flush Pankaj Gupta
2021-03-11 16:31 ` David Hildenbrand [this message]
2021-03-12 4:21 ` [RFC 0/2] virtio-pmem: Asynchronous flush Pankaj Gupta
2021-03-12 6:02 ` Dan Williams
2021-03-12 8:53 ` David Hildenbrand
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=7e55abc4-5c91-efb8-1b32-87570dde62cc@redhat.com \
--to=david@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mst@redhat.com \
--cc=pankaj.gupta.linux@gmail.com \
--cc=pankaj.gupta@cloud.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
all inboxes | Powered by JetHome®