From: Dave Jiang <dave.jiang@intel.com>
To: Stephen Bates <sbates@raithlin.com>,
Logan Gunthorpe <logang@deltatee.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: dmaengine support for PMEM
Date: Tue, 21 Aug 2018 10:52:01 -0700 [thread overview]
Message-ID: <8d55e740-8caf-1b4d-6507-d18f99a309e6@intel.com> (raw)
In-Reply-To: <A88D23C5-46BD-462D-92D7-22BF284A905C@raithlin.com>
On 08/21/2018 10:37 AM, Stephen Bates wrote:
> Hi Dave
>
> I hope you are well. Logan and I were looking at adding DMA support to PMEM and then were informed you have proposed some patches to do just that for the ioat DMA engine. The latest version of those I can see were the v7 from August 2017. Is there a more recent version? What happened to that series?
>
> https://lists.01.org/pipermail/linux-nvdimm/2017-August/012208.html
>
> Cheers
>
> Stephen
>
>
Hi Guys. Nothing has happened...yet... It's just on hold for now.
Here's where I left it last
https://git.kernel.org/pub/scm/linux/kernel/git/djiang/linux.git/log/?h=pmem_blk_dma
I do think we need to do some rework with the dmaengine in order to get
better efficiency as well. At some point I would like to see a call in
dmaengine that will take a request (similar to mq) and just operate on
that and submit the descriptors in a single call. I think that can
possibly deprecate all the host of function pointers for dmaengine. I'm
hoping to find some time to take a look at some of this work towards the
end of the year. But I'd be highly interested if you guys have ideas and
thoughts on this topic. And you are welcome to take my patches and run
with it.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-08-21 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 17:37 dmaengine support for PMEM Stephen Bates
2018-08-21 17:52 ` Dave Jiang [this message]
2018-08-21 18:07 ` Stephen Bates
2018-08-21 18:11 ` Dave Jiang
2018-08-21 18:13 ` Logan Gunthorpe
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=8d55e740-8caf-1b4d-6507-d18f99a309e6@intel.com \
--to=dave.jiang@intel.com \
--cc=linux-nvdimm@lists.01.org \
--cc=logang@deltatee.com \
--cc=sbates@raithlin.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).