All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH] Allow to use DMA_CTRL_REUSE flag for all channel types
Date: Tue, 2 May 2017 15:16:18 +0000	[thread overview]
Message-ID: <1493738176.25985.23.camel@synopsys.com> (raw)
In-Reply-To: <20170501055125.GN6263@localhost>

Hi Vinod,

On Mon, 2017-05-01@11:21 +0530, Vinod Koul wrote:
> On Fri, Apr 28, 2017@04:37:46PM +0300, Eugeniy Paltsev wrote:
> > In the current implementation dma_get_slave_caps is used to check
> > state of descriptor_reuse option. But dma_get_slave_caps includes
> > check if the channel supports slave transactions.
> > So DMA_CTRL_REUSE flag can be set (even for MEM-TO-MEM tranfers)
> > only if channel supports slave transactions.
> > 
> > Now we can use DMA_CTRL_REUSE flag for all channel types.
> > Also it allows to test reusing mechanism with simply mem-to-mem dma
> > test.
> 
> We do not want to allow that actually. Slave is always treated as a
> special
> case, so resue was allowed.
> 
> With memcpy the assumptions are different and clients can do reuse.

Could you please clarify why don't we want to allow use DMA_CTRL_REUSE
for mem-to-mem transfers?

Reusing of mem-to-mem (MEMCPY and DMA_SG) descriptors will work fine on
virt-dma based drivers.

Anyway the current implementation behaviour is quite strange:
If channel supports *slave* transfers DMA_CTRL_REUSE can be set to
slave and *mem-to-mem* transfers.

And, of course, we can pass DMA_CTRL_REUSE flag to device_prep_dma_sg
or device_prep_dma_memcpy directly without checks.

> > 
> > Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev at synopsys.com>
> > ---
> > ?include/linux/dmaengine.h | 6 +-----
> > ?1 file changed, 1 insertion(+), 5 deletions(-)
> > 
> > diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
> > index 5336808..92cf8b0 100644
> > --- a/include/linux/dmaengine.h
> > +++ b/include/linux/dmaengine.h
> > @@ -1376,11 +1376,7 @@ static inline int dma_get_slave_caps(struct
> > dma_chan *chan,
> > ?
> > ?static inline int dmaengine_desc_set_reuse(struct
> > dma_async_tx_descriptor *tx)
> > ?{
> > -	struct dma_slave_caps caps;
> > -
> > -	dma_get_slave_caps(tx->chan, &caps);
> > -
> > -	if (caps.descriptor_reuse) {
> > +	if (tx->chan->device->descriptor_reuse) {
> > ?		tx->flags |= DMA_CTRL_REUSE;
> > ?		return 0;
> > ?	} else {
> > --?
> > 2.9.3
> > 
> > --
-- 
?Eugeniy Paltsev

WARNING: multiple messages have this Message-ID (diff)
From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: "vinod.koul@intel.com" <vinod.koul@intel.com>
Cc: "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"andriy.shevchenko@linux.intel.com" 
	<andriy.shevchenko@linux.intel.com>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"Alexey.Brodkin@synopsys.com" <Alexey.Brodkin@synopsys.com>,
	"Eugeniy.Paltsev@synopsys.com" <Eugeniy.Paltsev@synopsys.com>,
	"linux-snps-arc@lists.infradead.org" 
	<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH] Allow to use DMA_CTRL_REUSE flag for all channel types
Date: Tue, 2 May 2017 15:16:18 +0000	[thread overview]
Message-ID: <1493738176.25985.23.camel@synopsys.com> (raw)
In-Reply-To: <20170501055125.GN6263@localhost>

Hi Vinod,

On Mon, 2017-05-01 at 11:21 +0530, Vinod Koul wrote:
> On Fri, Apr 28, 2017 at 04:37:46PM +0300, Eugeniy Paltsev wrote:
> > In the current implementation dma_get_slave_caps is used to check
> > state of descriptor_reuse option. But dma_get_slave_caps includes
> > check if the channel supports slave transactions.
> > So DMA_CTRL_REUSE flag can be set (even for MEM-TO-MEM tranfers)
> > only if channel supports slave transactions.
> > 
> > Now we can use DMA_CTRL_REUSE flag for all channel types.
> > Also it allows to test reusing mechanism with simply mem-to-mem dma
> > test.
> 
> We do not want to allow that actually. Slave is always treated as a
> special
> case, so resue was allowed.
> 
> With memcpy the assumptions are different and clients can do reuse.

Could you please clarify why don't we want to allow use DMA_CTRL_REUSE
for mem-to-mem transfers?

Reusing of mem-to-mem (MEMCPY and DMA_SG) descriptors will work fine on
virt-dma based drivers.

Anyway the current implementation behaviour is quite strange:
If channel supports *slave* transfers DMA_CTRL_REUSE can be set to
slave and *mem-to-mem* transfers.

And, of course, we can pass DMA_CTRL_REUSE flag to device_prep_dma_sg
or device_prep_dma_memcpy directly without checks.

> > 
> > Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
> > ---
> >  include/linux/dmaengine.h | 6 +-----
> >  1 file changed, 1 insertion(+), 5 deletions(-)
> > 
> > diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
> > index 5336808..92cf8b0 100644
> > --- a/include/linux/dmaengine.h
> > +++ b/include/linux/dmaengine.h
> > @@ -1376,11 +1376,7 @@ static inline int dma_get_slave_caps(struct
> > dma_chan *chan,
> >  
> >  static inline int dmaengine_desc_set_reuse(struct
> > dma_async_tx_descriptor *tx)
> >  {
> > -	struct dma_slave_caps caps;
> > -
> > -	dma_get_slave_caps(tx->chan, &caps);
> > -
> > -	if (caps.descriptor_reuse) {
> > +	if (tx->chan->device->descriptor_reuse) {
> >  		tx->flags |= DMA_CTRL_REUSE;
> >  		return 0;
> >  	} else {
> > -- 
> > 2.9.3
> > 
> > --
-- 
 Eugeniy Paltsev

  reply	other threads:[~2017-05-02 15:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28 13:37 [PATCH] Allow to use DMA_CTRL_REUSE flag for all channel types Eugeniy Paltsev
2017-04-28 13:37 ` Eugeniy Paltsev
2017-05-01  5:51 ` Vinod Koul
2017-05-01  5:51   ` Vinod Koul
2017-05-02 15:16   ` Eugeniy Paltsev [this message]
2017-05-02 15:16     ` Eugeniy Paltsev
2017-05-10  3:55     ` Vinod Koul
2017-05-10  3:55       ` Vinod Koul

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=1493738176.25985.23.camel@synopsys.com \
    --to=eugeniy.paltsev@synopsys.com \
    --cc=linux-snps-arc@lists.infradead.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 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.