mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Huan Yang <link@vivo.com>
To: "Kasireddy, Vivek" <vivek.kasireddy@intel.com>,
	"Sumit Semwal" <sumit.semwal@linaro.org>,
	"Christian König" <christian.koenig@amd.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "opensource.kernel@vivo.com" <opensource.kernel@vivo.com>
Subject: Re: [PATCH v5 6/7] udmabuf: remove udmabuf_folio
Date: Fri, 6 Sep 2024 16:39:39 +0800	[thread overview]
Message-ID: <d1e5d883-1ade-4d68-a240-9ac0301d2baf@vivo.com> (raw)
In-Reply-To: <IA0PR11MB718551FE1B9B9D4CC7956144F89E2@IA0PR11MB7185.namprd11.prod.outlook.com>


在 2024/9/6 16:22, Kasireddy, Vivek 写道:
> Hi Huan,
>
>> Subject: [PATCH v5 6/7] udmabuf: remove udmabuf_folio
>>
>> Currently, udmabuf handles folio by creating an unpin list to record
>> each folio obtained from the list and unpinning them when released. To
>> maintain this approach, many data structures have been established.
>>
>> However, maintaining this type of data structure requires a significant
>> amount of memory and traversing the list is a substantial overhead,
>> which is not friendly to the CPU cache.
>>
>> Considering that during creation, we arranged the folio array in the
>> order of pin and set the offset according to pgcnt.
>>
>> We actually don't need to use unpin_list to unpin during release.
>> Instead, we can iterate through the folios array during release and
>> unpin any folio that is different from the ones previously accessed.
>>
>> By this, not only saves the overhead of the udmabuf_folio data structure
>> but also makes array access more cache-friendly.
>>
>> Signed-off-by: Huan Yang <link@vivo.com>
>> ---
>>   drivers/dma-buf/udmabuf.c | 65 +++++++++++++++++----------------------
>>   1 file changed, 29 insertions(+), 36 deletions(-)
>>
>> diff --git a/drivers/dma-buf/udmabuf.c b/drivers/dma-buf/udmabuf.c
>> index 254d9ec3d9f3..d449c1fd67a5 100644
>> --- a/drivers/dma-buf/udmabuf.c
>> +++ b/drivers/dma-buf/udmabuf.c
>> @@ -27,15 +27,21 @@ MODULE_PARM_DESC(size_limit_mb, "Max size of a
>> dmabuf, in megabytes. Default is
>>   struct udmabuf {
>>   	pgoff_t pagecount;
>>   	struct folio **folios;
>> +
>> +	/**
>> +	 * Unlike folios, pinned_folios is only used for unpin.
>> +	 * So, nr_pinned is not the same to pagecount, the pinned_folios
>> +	 * only set each folio which already pinned when udmabuf_create.
>> +	 * Note that, since a folio may be pinned multiple times, each folio
>> +	 * can be added to pinned_folios multiple times, depending on how
>> many
>> +	 * times the folio has been pinned when create.
>> +	 */
>> +	pgoff_t nr_pinned;
>> +	struct folio **pinned_folios;
>> +
>>   	struct sg_table *sg;
>>   	struct miscdevice *device;
>>   	pgoff_t *offsets;
>> -	struct list_head unpin_list;
>> -};
>> -
>> -struct udmabuf_folio {
>> -	struct folio *folio;
>> -	struct list_head list;
>>   };
>>
>>   static vm_fault_t udmabuf_vm_fault(struct vm_fault *vmf)
>> @@ -198,38 +204,18 @@ static void unmap_udmabuf(struct
>> dma_buf_attachment *at,
>>   	return put_sg_table(at->dev, sg, direction);
>>   }
>>
>> -static void unpin_all_folios(struct list_head *unpin_list)
>> +static void unpin_all_folios(struct udmabuf *ubuf)
>>   {
>> -	struct udmabuf_folio *ubuf_folio;
>> +	pgoff_t i;
>>
>> -	while (!list_empty(unpin_list)) {
>> -		ubuf_folio = list_first_entry(unpin_list,
>> -					      struct udmabuf_folio, list);
>> -		unpin_folio(ubuf_folio->folio);
>> +	for (i = 0; i < ubuf->nr_pinned; ++i)
>> +		unpin_folio(ubuf->pinned_folios[i]);
>>
>> -		list_del(&ubuf_folio->list);
>> -		kfree(ubuf_folio);
>> -	}
>> -}
>> -
>> -static int add_to_unpin_list(struct list_head *unpin_list,
>> -			     struct folio *folio)
>> -{
>> -	struct udmabuf_folio *ubuf_folio;
>> -
>> -	ubuf_folio = kzalloc(sizeof(*ubuf_folio), GFP_KERNEL);
>> -	if (!ubuf_folio)
>> -		return -ENOMEM;
>> -
>> -	ubuf_folio->folio = folio;
>> -	list_add_tail(&ubuf_folio->list, unpin_list);
>> -	return 0;
>> +	kvfree(ubuf->pinned_folios);
>>   }
>>
>>   static __always_inline int init_udmabuf(struct udmabuf *ubuf, pgoff_t
>> pgcnt)
>>   {
>> -	INIT_LIST_HEAD(&ubuf->unpin_list);
>> -
>>   	ubuf->folios = kvmalloc_array(pgcnt, sizeof(*ubuf->folios),
>> GFP_KERNEL);
>>   	if (!ubuf->folios)
>>   		return -ENOMEM;
>> @@ -238,12 +224,18 @@ static __always_inline int init_udmabuf(struct
>> udmabuf *ubuf, pgoff_t pgcnt)
>>   	if (!ubuf->offsets)
>>   		return -ENOMEM;
>>
>> +	ubuf->pinned_folios = kvmalloc_array(pgcnt,
>> +					     sizeof(*ubuf->pinned_folios),
>> +					     GFP_KERNEL);
>> +	if (!ubuf->pinned_folios)
>> +		return -ENOMEM;
>> +
>>   	return 0;
>>   }
>>
>>   static __always_inline void deinit_udmabuf(struct udmabuf *ubuf)
>>   {
>> -	unpin_all_folios(&ubuf->unpin_list);
>> +	unpin_all_folios(ubuf);
>>   	kvfree(ubuf->offsets);
>>   	kvfree(ubuf->folios);
>>   }
>> @@ -353,7 +345,9 @@ static int export_udmabuf(struct udmabuf *ubuf,
>>   static int udmabuf_pin_folios(struct udmabuf *ubuf, struct file *memfd,
>>   			      loff_t start, loff_t size)
>>   {
>> -	pgoff_t pgoff, pgcnt, upgcnt = ubuf->pagecount;
>> +	pgoff_t pgoff, pgcnt;
>> +	pgoff_t upgcnt = ubuf->pagecount;
>> +	pgoff_t nr_pinned = ubuf->nr_pinned;
> Reverse xmas style is preferred; please try to use that.

OK, I'll take care of it, and other patch. :)

>
>>   	u32 cur_folio, cur_pgcnt;
>>   	struct folio **folios = NULL;
>>   	long nr_folios;
>> @@ -377,9 +371,7 @@ static int udmabuf_pin_folios(struct udmabuf *ubuf,
>> struct file *memfd,
>>   		pgoff_t subpgoff = pgoff;
>>   		size_t fsize = folio_size(folios[cur_folio]);
>>
>> -		ret = add_to_unpin_list(&ubuf->unpin_list, folios[cur_folio]);
>> -		if (ret < 0)
>> -			goto err;
>> +		ubuf->pinned_folios[nr_pinned++] = folios[cur_folio];
>>
>>   		for (; subpgoff < fsize; subpgoff += PAGE_SIZE) {
>>   			ubuf->folios[upgcnt] = folios[cur_folio];
>> @@ -399,6 +391,7 @@ static int udmabuf_pin_folios(struct udmabuf *ubuf,
>> struct file *memfd,
>>   end:
>>   err:
>>   	ubuf->pagecount = upgcnt;
>> +	ubuf->nr_pinned = nr_pinned;
> Acked-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
>
>>   	kvfree(folios);
>>   	return ret;
>>   }
>> --
>> 2.45.2

  reply	other threads:[~2024-09-06  8:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03  8:38 [PATCH v5 0/7] udmbuf bug fix and some improvements Huan Yang
2024-09-03  8:38 ` [PATCH v5 1/7] udmabuf: pre-fault when first page fault Huan Yang
2024-09-06  8:12   ` Kasireddy, Vivek
2024-09-06  8:37     ` Huan Yang
2024-09-03  8:38 ` [PATCH v5 2/7] udmabuf: change folios array from kmalloc to kvmalloc Huan Yang
2024-09-03  8:38 ` [PATCH v5 3/7] udmabuf: fix vmap_udmabuf error page set Huan Yang
2024-09-03  8:38 ` [PATCH v5 4/7] udmabuf: udmabuf_create pin folio codestyle cleanup Huan Yang
2024-09-06  8:17   ` Kasireddy, Vivek
2024-09-06  8:30     ` Huan Yang
2024-09-09  5:03       ` Kasireddy, Vivek
2024-09-09  6:31         ` Huan Yang
2024-09-03  8:38 ` [PATCH v5 5/7] udmabuf: introduce udmabuf init and deinit helper Huan Yang
2024-09-06  8:20   ` Kasireddy, Vivek
2024-09-06  8:38     ` Huan Yang
2024-09-03  8:38 ` [PATCH v5 6/7] udmabuf: remove udmabuf_folio Huan Yang
2024-09-06  8:22   ` Kasireddy, Vivek
2024-09-06  8:39     ` Huan Yang [this message]
2024-09-03  8:38 ` [PATCH v5 7/7] udmabuf: reuse folio array when pin folios Huan Yang
2024-09-06  8:23   ` Kasireddy, Vivek
2024-09-06  8:40     ` Huan Yang

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=d1e5d883-1ade-4d68-a240-9ac0301d2baf@vivo.com \
    --to=link@vivo.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kraxel@redhat.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=opensource.kernel@vivo.com \
    --cc=sumit.semwal@linaro.org \
    --cc=vivek.kasireddy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®