All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: vinod.koul@intel.com, dan.j.williams@intel.com
Cc: dmaengine@vger.kernel.org, hch@infradead.org, linux-nvdimm@lists.01.org
Subject: [PATCH v6 1/8] dmaengine: ioatdma: revert 7618d035 to allow sharing of DMA channels
Date: Fri, 25 Aug 2017 13:59:30 -0700	[thread overview]
Message-ID: <150369477016.6962.8636764604054663107.stgit@djiang5-desk3.ch.intel.com> (raw)
In-Reply-To: <150369446130.6962.4195769527575520889.stgit@djiang5-desk3.ch.intel.com>

Commit 7618d0359c16 ("dmaengine: ioatdma: Set non RAID channels to be
private capable") makes all non-RAID ioatdma channels as private to be
requestable by dma_request_channel(). With PQ CAP support going away for
ioatdma, this would make all channels private. To support the usage of
ioatdma for blk-mq implementation of pmem we need as many channels we can
share in order to be high performing. Thus reverting the patch.

Signed-off-by: Dave Jiang <dave.jiang@intel.com>
---
 drivers/dma/ioat/init.c |    3 ---
 1 file changed, 3 deletions(-)

diff --git a/drivers/dma/ioat/init.c b/drivers/dma/ioat/init.c
index ed8ed11..1b881fb 100644
--- a/drivers/dma/ioat/init.c
+++ b/drivers/dma/ioat/init.c
@@ -1153,9 +1153,6 @@ static int ioat3_dma_probe(struct ioatdma_device *ioat_dma, int dca)
 		}
 	}
 
-	if (!(ioat_dma->cap & (IOAT_CAP_XOR | IOAT_CAP_PQ)))
-		dma_cap_set(DMA_PRIVATE, dma->cap_mask);
-
 	err = ioat_probe(ioat_dma);
 	if (err)
 		return err;

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  reply	other threads:[~2017-08-25 20:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 20:59 [PATCH v6 0/8] libnvdimm: add DMA supported blk-mq pmem driver Dave Jiang
2017-08-25 20:59 ` Dave Jiang [this message]
2017-08-25 20:59 ` [PATCH v6 2/8] dmaengine: Add DMA_MEMCPY_SG transaction op Dave Jiang
2017-08-30 18:18   ` [v6,2/8] " Robin Murphy
2017-08-30 18:25     ` Dave Jiang
2017-08-31 10:57       ` Robin Murphy
2017-11-13  8:28         ` Stefan Roese
2017-11-15 15:52           ` Vinod Koul
2017-11-15 16:13             ` Stefan Roese
2017-11-15 16:37               ` Dave Jiang
2017-08-25 20:59 ` [PATCH v6 3/8] dmaengine: add verification of DMA_MEMSET_SG in dmaengine Dave Jiang
2017-08-25 20:59 ` [PATCH v6 4/8] dmaengine: ioatdma: dma_prep_memcpy_sg support Dave Jiang
2017-08-25 20:59 ` [PATCH v6 5/8] dmaengine: add function to provide per descriptor xfercap for dma engine Dave Jiang
2017-08-25 20:59 ` [PATCH v6 6/8] dmaengine: add SG support to dmaengine_unmap Dave Jiang
2017-08-25 21:00 ` [PATCH v6 7/8] dmaengine: provide number of available channels Dave Jiang
2017-08-25 21:00 ` [PATCH v6 8/8] libnvdimm: Add blk-mq pmem driver Dave Jiang
2017-08-25 23:08   ` Dan Williams

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=150369477016.6962.8636764604054663107.stgit@djiang5-desk3.ch.intel.com \
    --to=dave.jiang@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=vinod.koul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.