Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp2869793ybk; Tue, 12 May 2020 10:03:57 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxgJyf6tLik6OxsKK7RrV1uaE9mhB7TQ5hwQutvkvfLBNGEDNYuyVdjAlBg5ObkM/DqjSaY X-Received: by 2002:a17:906:410a:: with SMTP id j10mr8966990ejk.378.1589303037007; Tue, 12 May 2020 10:03:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589303037; cv=none; d=google.com; s=arc-20160816; b=UFd02+vvzXO98cyeXn9kK2oIJkdtJXoc1Y1CBPYz7CoT702ltl2hRiGAojllo54Rc1 qqYnapxu63BBkCYoGq14yGqTi/W1imZOC1wkaxM5WiROXAHuIqkkTEFuN49lkyi4dqKB vS+shNEWBm/QcOXw3raFuh9EtpGy3g+I3R4sp2LCy2OqMaLppOAoWrTwN5FFGZpj9K7k nI1F/BvTZV9xX/80wcEBH8kUfU+/b+VANY01Co73Ru3kzDCFQugyXa+O01kj3FciCzgN m38Bi+RukYdOlgDZbUaWS/XSBxAx2aZB+HxKERjHouBojz7AlrNd5YY1qsWZmpeUk+1B RO/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=w1nrGtmeAsmxOffdMnjRmj5KTOj0xRK53MfV1XBotJE=; b=NxaLFcIYUGUZ4P4L5W+g0gtUWGsb9epn0PNMJiZIOlS/hvfd70JftdEOqlHUBd4HjW FHv7CUC9wlMa7VrILms8/HNEkWL+U/VHvtZZ4meclUBP27K3RAnuEdvO+kz861R+4eUI dmh5xRJmgj9Ss+s0ztLBmwfNumBukr72dcalqcmTU53VdxB7MN93n5P/s6Ag1lDm24Qr txiHLUh629BdlSBeovoJFJFw76kHoewcO3EdXUQt+R9kmnGQ/fA3/Sdt3DdxYHXSTJ+U Gk9d7PaUrzlIqIwhkgaUzokYH//OzCNi1FYk4wymL7LWktY0gdfuQMkQhrwkxEUlHBPN x6xg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 62si8748337edc.448.2020.05.12.10.03.28; Tue, 12 May 2020 10:03:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728309AbgELRBY (ORCPT + 99 others); Tue, 12 May 2020 13:01:24 -0400 Received: from mail.baikalelectronics.com ([87.245.175.226]:54412 "EHLO mail.baikalelectronics.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725554AbgELRBY (ORCPT ); Tue, 12 May 2020 13:01:24 -0400 Received: from localhost (unknown [127.0.0.1]) by mail.baikalelectronics.ru (Postfix) with ESMTP id 33F65803080B; Tue, 12 May 2020 17:01:21 +0000 (UTC) X-Virus-Scanned: amavisd-new at baikalelectronics.ru Received: from mail.baikalelectronics.ru ([127.0.0.1]) by localhost (mail.baikalelectronics.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IZmXehCXf_Nc; Tue, 12 May 2020 20:01:20 +0300 (MSK) Date: Tue, 12 May 2020 20:01:18 +0300 From: Serge Semin To: Andy Shevchenko CC: Serge Semin , Vineet Gupta , Vinod Koul , Viresh Kumar , Dan Williams , Alexey Malahov , Thomas Bogendoerfer , Paul Burton , Ralf Baechle , Arnd Bergmann , Rob Herring , , , , Subject: Re: [PATCH v2 3/6] dmaengine: dw: Set DMA device max segment size parameter Message-ID: <20200512170118.3qbtpuphtwltb7nu@mobilestation> References: <20200306131048.ADBE18030797@mail.baikalelectronics.ru> <20200508105304.14065-1-Sergey.Semin@baikalelectronics.ru> <20200508105304.14065-4-Sergey.Semin@baikalelectronics.ru> <20200508112152.GI185537@smile.fi.intel.com> <20200511211622.yuh3ls2ay76yaxrf@mobilestation> <20200512123551.GX185537@smile.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20200512123551.GX185537@smile.fi.intel.com> X-ClientProxiedBy: MAIL.baikal.int (192.168.51.25) To mail (192.168.51.25) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 12, 2020 at 03:35:51PM +0300, Andy Shevchenko wrote: > On Tue, May 12, 2020 at 12:16:22AM +0300, Serge Semin wrote: > > On Fri, May 08, 2020 at 02:21:52PM +0300, Andy Shevchenko wrote: > > > On Fri, May 08, 2020 at 01:53:01PM +0300, Serge Semin wrote: > > > > Maximum block size DW DMAC configuration corresponds to the max segment > > > > size DMA parameter in the DMA core subsystem notation. Lets set it with a > > > > value specific to the probed DW DMA controller. It shall help the DMA > > > > clients to create size-optimized SG-list items for the controller. This in > > > > turn will cause less dw_desc allocations, less LLP reinitializations, > > > > better DMA device performance. > > > > Yeah, I have locally something like this and I didn't dare to upstream because > > > there is an issue. We have this information per DMA controller, while we > > > actually need this on per DMA channel basis. > > > > > > Above will work only for synthesized DMA with all channels having same block > > > size. That's why above conditional is not needed anyway. > > > > Hm, I don't really see why the conditional isn't needed and this won't work. As > > you can see in the loop above Initially I find a maximum of all channels maximum > > block sizes and use it then as a max segment size parameter for the whole device. > > If the DW DMA controller has the same max block size of all channels, then it > > will be found. If the channels've been synthesized with different block sizes, > > then the optimization will work for the one with greatest block size. The SG > > list entries of the channels with lesser max block size will be split up > > by the DW DMAC driver, which would have been done anyway without > > max_segment_size being set. Here we at least provide the optimization for the > > channels with greatest max block size. > > > > I do understand that it would be good to have this parameter setup on per generic > > DMA channel descriptor basis. But DMA core and device descriptor doesn't provide > > such facility, so setting at least some justified value is a good idea. > > > > > > > > OTOH, I never saw the DesignWare DMA to be synthesized differently (I remember > > > that Intel Medfield has interesting settings, but I don't remember if DMA > > > channels are different inside the same controller). > > > > > > Vineet, do you have any information that Synopsys customers synthesized DMA > > > controllers with different channel characteristics inside one DMA IP? > > > > AFAICS the DW DMAC channels can be synthesized with different max block size. > > The IP core supports such configuration. So we can't assume that such DMAC > > release can't be found in a real hardware just because we've never seen one. > > No matter what Vineet will have to say in response to your question. > > My point here that we probably can avoid complications till we have real > hardware where it's different. As I said I don't remember a such, except > *maybe* Intel Medfield, which is quite outdated and not supported for wider > audience anyway. I see your point. My position is different in this matter and explained in the previous emails. Let's see what Viresh and Vinod think of it. -Sergey > > -- > With Best Regards, > Andy Shevchenko > >