public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Bingbu Cao <bingbu.cao@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>, bingbu.cao@intel.com
Cc: linux-media@vger.kernel.org, jianhui.j.dai@intel.com, tfiga@chromium.org
Subject: Re: [PATCH v2] media: intel/ipu6: optimize the IPU6 MMU mapping and unmapping flow
Date: Tue, 22 Oct 2024 08:39:47 +0800	[thread overview]
Message-ID: <e97d9747-b6f3-bda6-874b-e6435e283bd9@linux.intel.com> (raw)
In-Reply-To: <ZxYShNcSzFMwap6G@kekkonen.localdomain>

Sakari,

Thank you for the review.

On 10/21/24 4:36 PM, Sakari Ailus wrote:
> Hi Bingbu,
> 
> On Fri, Aug 16, 2024 at 11:31:21AM +0800, bingbu.cao@intel.com wrote:
>> From: Bingbu Cao <bingbu.cao@intel.com>
>>
>> ipu6_mmu_map() and ipu6_mmu_unmap() operated on a per-page basis,
>> leading to frequent calls to spin_locks/unlocks and
>> clflush_cache_range for each page. This will cause inefficiencies,
>> especially when handling large dma-bufs with hundreds of pages.
>>
>> This change enhances ipu6_mmu_map()/ipu6_mmu_unmap() with batching
>> process multiple contiguous pages. This significantly reduces calls
>> for spin_lock/unlock and clflush_cache_range() and improve the
>> performance.
>>
>> Signed-off-by: Jianhui Dai <jianhui.j.dai@intel.com>
>> Signed-off-by: Bingbu Cao <bingbu.cao@intel.com>
> 
> Thanks for the patch.
> 
> Could you split this into three patches (at least) to make it more
> reviewable:
> 
> - Move l2_unmap() up to its new location.
> - Add unmapping optimisation.
> - Add mapping optimisation.
> 

Yes, I will split this.

-- 
Best regards,
Bingbu Cao

      reply	other threads:[~2024-10-22  0:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16  3:31 [PATCH v2] media: intel/ipu6: optimize the IPU6 MMU mapping and unmapping flow bingbu.cao
2024-09-03  8:28 ` Bingbu Cao
2024-09-09  2:31   ` Yan, Dongcheng
2024-09-12  1:20 ` Bingbu Cao
2024-10-03 11:15 ` Sakari Ailus
2024-10-08  1:40   ` Cao, Bingbu
2024-10-21  8:36 ` Sakari Ailus
2024-10-22  0:39   ` Bingbu Cao [this message]

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=e97d9747-b6f3-bda6-874b-e6435e283bd9@linux.intel.com \
    --to=bingbu.cao@linux.intel.com \
    --cc=bingbu.cao@intel.com \
    --cc=jianhui.j.dai@intel.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=tfiga@chromium.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