From: Vinod Koul <vinod.koul@intel.com>
To: "Jiang, Dave" <dave.jiang@intel.com>, \
Cc: Sinan Kaya <okaya@codeaurora.org>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH v2 5/5] libnvdimm: add DMA support for pmem blk-mq
Date: Thu, 3 Aug 2017 10:58:17 +0530 [thread overview]
Message-ID: <20170803052817.GF3053@localhost> (raw)
In-Reply-To: <423B07FD-31B3-424B-849E-FAC5C0AD8FAE@intel.com>
On Thu, Aug 03, 2017 at 10:41:51AM +0530, Jiang, Dave wrote:
>
>
> > On Aug 2, 2017, at 9:58 PM, Koul, Vinod <vinod.koul@intel.com> wrote:
> >
> >> On Wed, Aug 02, 2017 at 02:13:56PM -0700, Dave Jiang wrote:
> >>
> >>
> >>> On 08/02/2017 02:10 PM, Sinan Kaya wrote:
> >>> On 8/2/2017 4:52 PM, Dave Jiang wrote:
> >>>>> Do we need a new API / new function, or new capability?
> >>>> Hmmm...you are right. I wonder if we need something like DMA_SG cap....
> >>>>
> >>>>
> >>>
> >>> Unfortunately, DMA_SG means something else. Maybe, we need DMA_MEMCPY_SG
> >>> to be similar with DMA_MEMSET_SG.
> >>
> >> I'm ok with that if Vinod is.
> >
> > So what exactly is the ask here, are you trying to do MEMCPY or SG or MEMSET
> > or all :). We should have done bitfields for this though...
>
> Add DMA_MEMCPY_SG to transaction type.
Not MEMSET right, then why not use DMA_SG, DMA_SG is supposed for
scatterlist to scatterlist copy which is used to check for
device_prep_dma_sg() calls
--
~Vinod
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2017-08-03 5:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 18:40 [PATCH v2 0/5] Adding blk-mq and DMA support to pmem block driver Dave Jiang
2017-08-02 18:41 ` [PATCH v2 1/5] dmaengine: ioatdma: revert 7618d035 to allow sharing of DMA channels Dave Jiang
2017-08-02 18:41 ` [PATCH v2 2/5] dmaengine: ioatdma: dma_prep_memcpy_sg support Dave Jiang
2017-08-02 18:41 ` [PATCH v2 3/5] dmaengine: add SG support to dmaengine_unmap Dave Jiang
2017-08-02 18:41 ` [PATCH v2 4/5] libnvdimm: Adding blk-mq support to the pmem driver Dave Jiang
2017-08-03 20:04 ` Ross Zwisler
2017-08-02 18:41 ` [PATCH v2 5/5] libnvdimm: add DMA support for pmem blk-mq Dave Jiang
2017-08-02 19:22 ` Sinan Kaya
2017-08-02 20:52 ` Dave Jiang
2017-08-02 21:10 ` Sinan Kaya
2017-08-02 21:13 ` Dave Jiang
2017-08-03 5:01 ` Vinod Koul
2017-08-03 5:11 ` Jiang, Dave
2017-08-03 5:28 ` Vinod Koul [this message]
2017-08-03 5:36 ` Jiang, Dave
2017-08-03 8:59 ` Vinod Koul
2017-08-03 14:36 ` Jiang, Dave
2017-08-03 15:55 ` Vinod Koul
2017-08-03 16:14 ` Dan Williams
2017-08-03 17:07 ` Dave Jiang
2017-08-03 18:35 ` Allen Hubbe
2017-08-16 16:50 ` Vinod Koul
2017-08-16 17:06 ` Dan Williams
2017-08-16 17:16 ` Dave Jiang
2017-08-16 17:20 ` Dan Williams
2017-08-16 17:27 ` Dave Jiang
2017-08-18 5:35 ` Vinod Koul
2017-08-03 20:20 ` Ross Zwisler
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=20170803052817.GF3053@localhost \
--to=vinod.koul@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=okaya@codeaurora.org \
/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