All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Paul Cercueil <paul@crapouillou.net>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"Alexandru Ardelean" <ardeleanalex@gmail.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Sumit Semwal" <sumit.semwal@linaro.org>,
	"Christian König" <christian.koenig@amd.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH 01/15] iio: buffer-dma: Get rid of incoming/outgoing queues
Date: Sun, 21 Nov 2021 19:49:03 +0100	[thread overview]
Message-ID: <332d001d-8b5a-bba2-c490-ed2e5efd0b1d@metafoo.de> (raw)
In-Reply-To: <0COX2R.BSNX3NW8N48T@crapouillou.net>

On 11/21/21 6:52 PM, Paul Cercueil wrote:
> Hi Lars,
>
> Le dim., nov. 21 2021 at 17:23:35 +0100, Lars-Peter Clausen 
> <lars@metafoo.de> a écrit :
>> On 11/15/21 3:19 PM, Paul Cercueil wrote:
>>> The buffer-dma code was using two queues, incoming and outgoing, to
>>> manage the state of the blocks in use.
>>>
>>> While this totally works, it adds some complexity to the code,
>>> especially since the code only manages 2 blocks. It is much easier to
>>> just check each block's state manually, and keep a counter for the next
>>> block to dequeue.
>>>
>>> Since the new DMABUF based API wouldn't use these incoming and outgoing
>>> queues anyway, getting rid of them now makes the upcoming changes
>>> simpler.
>>>
>>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>> The outgoing queue is going to be replaced by fences, but I think we 
>> need to keep the incoming queue.
>
> Blocks are always accessed in sequential order, so we now have a 
> "queue->next_dequeue" that cycles between the buffers allocated for 
> fileio.
>
>>> [...]
>>> @@ -442,28 +435,33 @@ EXPORT_SYMBOL_GPL(iio_dma_buffer_disable);
>>>   static void iio_dma_buffer_enqueue(struct iio_dma_buffer_queue 
>>> *queue,
>>>       struct iio_dma_buffer_block *block)
>>>   {
>>> -    if (block->state == IIO_BLOCK_STATE_DEAD) {
>>> +    if (block->state == IIO_BLOCK_STATE_DEAD)
>>>           iio_buffer_block_put(block);
>>> -    } else if (queue->active) {
>>> +    else if (queue->active)
>>>           iio_dma_buffer_submit_block(queue, block);
>>> -    } else {
>>> +    else
>>>           block->state = IIO_BLOCK_STATE_QUEUED;
>>> -        list_add_tail(&block->head, &queue->incoming);
>> If iio_dma_buffer_enqueue() is called with a dmabuf and the buffer is 
>> not active, it will be marked as queued, but we don't actually keep a 
>> reference to it anywhere. It will never be submitted to the DMA, and 
>> it will never be signaled as completed.
>
> We do keep a reference to the buffers, in the queue->fileio.blocks 
> array. When the buffer is enabled, all the blocks in that array that 
> are in the "queued" state will be submitted to the DMA.
>
But not when used in combination with the DMA buf changes later in this 
series.


WARNING: multiple messages have this Message-ID (diff)
From: Lars-Peter Clausen <lars@metafoo.de>
To: Paul Cercueil <paul@crapouillou.net>
Cc: "Michael Hennerich" <Michael.Hennerich@analog.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
	"Alexandru Ardelean" <ardeleanalex@gmail.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH 01/15] iio: buffer-dma: Get rid of incoming/outgoing queues
Date: Sun, 21 Nov 2021 19:49:03 +0100	[thread overview]
Message-ID: <332d001d-8b5a-bba2-c490-ed2e5efd0b1d@metafoo.de> (raw)
In-Reply-To: <0COX2R.BSNX3NW8N48T@crapouillou.net>

On 11/21/21 6:52 PM, Paul Cercueil wrote:
> Hi Lars,
>
> Le dim., nov. 21 2021 at 17:23:35 +0100, Lars-Peter Clausen 
> <lars@metafoo.de> a écrit :
>> On 11/15/21 3:19 PM, Paul Cercueil wrote:
>>> The buffer-dma code was using two queues, incoming and outgoing, to
>>> manage the state of the blocks in use.
>>>
>>> While this totally works, it adds some complexity to the code,
>>> especially since the code only manages 2 blocks. It is much easier to
>>> just check each block's state manually, and keep a counter for the next
>>> block to dequeue.
>>>
>>> Since the new DMABUF based API wouldn't use these incoming and outgoing
>>> queues anyway, getting rid of them now makes the upcoming changes
>>> simpler.
>>>
>>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>> The outgoing queue is going to be replaced by fences, but I think we 
>> need to keep the incoming queue.
>
> Blocks are always accessed in sequential order, so we now have a 
> "queue->next_dequeue" that cycles between the buffers allocated for 
> fileio.
>
>>> [...]
>>> @@ -442,28 +435,33 @@ EXPORT_SYMBOL_GPL(iio_dma_buffer_disable);
>>>   static void iio_dma_buffer_enqueue(struct iio_dma_buffer_queue 
>>> *queue,
>>>       struct iio_dma_buffer_block *block)
>>>   {
>>> -    if (block->state == IIO_BLOCK_STATE_DEAD) {
>>> +    if (block->state == IIO_BLOCK_STATE_DEAD)
>>>           iio_buffer_block_put(block);
>>> -    } else if (queue->active) {
>>> +    else if (queue->active)
>>>           iio_dma_buffer_submit_block(queue, block);
>>> -    } else {
>>> +    else
>>>           block->state = IIO_BLOCK_STATE_QUEUED;
>>> -        list_add_tail(&block->head, &queue->incoming);
>> If iio_dma_buffer_enqueue() is called with a dmabuf and the buffer is 
>> not active, it will be marked as queued, but we don't actually keep a 
>> reference to it anywhere. It will never be submitted to the DMA, and 
>> it will never be signaled as completed.
>
> We do keep a reference to the buffers, in the queue->fileio.blocks 
> array. When the buffer is enabled, all the blocks in that array that 
> are in the "queued" state will be submitted to the DMA.
>
But not when used in combination with the DMA buf changes later in this 
series.


  reply	other threads:[~2021-11-21 18:49 UTC|newest]

Thread overview: 118+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 14:19 [PATCH 00/15] iio: buffer-dma: write() and new DMABUF based API Paul Cercueil
2021-11-15 14:19 ` Paul Cercueil
2021-11-15 14:19 ` [PATCH 01/15] iio: buffer-dma: Get rid of incoming/outgoing queues Paul Cercueil
2021-11-15 14:19   ` Paul Cercueil
2021-11-16  8:23   ` Alexandru Ardelean
2021-11-16  8:23     ` Alexandru Ardelean
2021-11-21 14:05   ` Jonathan Cameron
2021-11-21 14:05     ` Jonathan Cameron
2021-11-21 16:23   ` Lars-Peter Clausen
2021-11-21 16:23     ` Lars-Peter Clausen
2021-11-21 17:52     ` Paul Cercueil
2021-11-21 17:52       ` Paul Cercueil
2021-11-21 18:49       ` Lars-Peter Clausen [this message]
2021-11-21 18:49         ` Lars-Peter Clausen
2021-11-21 20:08         ` Paul Cercueil
2021-11-21 20:08           ` Paul Cercueil
2021-11-22 15:08           ` Lars-Peter Clausen
2021-11-22 15:08             ` Lars-Peter Clausen
2021-11-22 15:16             ` Paul Cercueil
2021-11-22 15:16               ` Paul Cercueil
2021-11-22 15:17               ` Lars-Peter Clausen
2021-11-22 15:17                 ` Lars-Peter Clausen
2021-11-22 15:27                 ` Paul Cercueil
2021-11-22 15:27                   ` Paul Cercueil
2021-11-15 14:19 ` [PATCH 02/15] iio: buffer-dma: Remove unused iio_buffer_block struct Paul Cercueil
2021-11-15 14:19   ` Paul Cercueil
2021-11-16  8:22   ` Alexandru Ardelean
2021-11-16  8:22     ` Alexandru Ardelean
2021-11-15 14:19 ` [PATCH 03/15] iio: buffer-dma: Use round_down() instead of rounddown() Paul Cercueil
2021-11-15 14:19   ` Paul Cercueil
2021-11-16  8:26   ` Alexandru Ardelean
2021-11-16  8:26     ` Alexandru Ardelean
2021-11-21 14:08   ` Jonathan Cameron
2021-11-21 14:08     ` Jonathan Cameron
2021-11-22 10:00     ` Paul Cercueil
2021-11-22 10:00       ` Paul Cercueil
2021-11-27 15:15       ` Jonathan Cameron
2021-11-27 15:15         ` Jonathan Cameron
2021-11-15 14:19 ` [PATCH 04/15] iio: buffer-dma: Enable buffer write support Paul Cercueil
2021-11-15 14:19   ` Paul Cercueil
2021-11-16  8:52   ` Alexandru Ardelean
2021-11-16  8:52     ` Alexandru Ardelean
2021-11-21 14:20   ` Jonathan Cameron
2021-11-21 14:20     ` Jonathan Cameron
2021-11-21 17:19     ` Paul Cercueil
2021-11-21 17:19       ` Paul Cercueil
2021-11-27 15:17       ` Jonathan Cameron
2021-11-27 15:17         ` Jonathan Cameron
2021-11-15 14:19 ` [PATCH 05/15] iio: buffer-dmaengine: Support specifying buffer direction Paul Cercueil
2021-11-15 14:19   ` Paul Cercueil
2021-11-16  8:53   ` Alexandru Ardelean
2021-11-16  8:53     ` Alexandru Ardelean
2021-11-15 14:19 ` [PATCH 06/15] iio: buffer-dmaengine: Enable write support Paul Cercueil
2021-11-15 14:19   ` Paul Cercueil
2021-11-16  8:55   ` Alexandru Ardelean
2021-11-16  8:55     ` Alexandru Ardelean
2021-11-15 14:19 ` [PATCH 07/15] iio: core: Add new DMABUF interface infrastructure Paul Cercueil
2021-11-15 14:19   ` Paul Cercueil
2021-11-21 14:31   ` Jonathan Cameron
2021-11-21 14:31     ` Jonathan Cameron
2021-11-15 14:19 ` [PATCH 08/15] iio: buffer-dma: split iio_dma_buffer_fileio_free() function Paul Cercueil
2021-11-15 14:19   ` Paul Cercueil
2021-11-16 10:59   ` Alexandru Ardelean
2021-11-16 10:59     ` Alexandru Ardelean
2021-11-21 13:49     ` Jonathan Cameron
2021-11-21 13:49       ` Jonathan Cameron
2021-11-15 14:19 ` [PATCH 09/15] iio: buffer-dma: Use DMABUFs instead of custom solution Paul Cercueil
2021-11-15 14:19   ` Paul Cercueil
2021-11-15 14:19 ` [PATCH 10/15] iio: buffer-dma: Implement new DMABUF based userspace API Paul Cercueil
2021-11-15 14:19   ` Paul Cercueil
2021-11-15 14:19 ` [PATCH 11/15] iio: buffer-dma: Boost performance using write-combine cache setting Paul Cercueil
2021-11-15 14:19   ` Paul Cercueil
2021-11-18 11:45   ` Paul Cercueil
2021-11-18 11:45     ` Paul Cercueil
2021-11-21 15:00   ` Jonathan Cameron
2021-11-21 15:00     ` Jonathan Cameron
2021-11-21 17:43     ` Paul Cercueil
2021-11-21 17:43       ` Paul Cercueil
2021-11-25 17:29       ` Paul Cercueil
2021-11-25 17:29         ` Paul Cercueil
2021-11-27 16:05         ` Jonathan Cameron
2021-11-27 16:05           ` Jonathan Cameron
2021-11-28 13:25           ` Lars-Peter Clausen
2021-11-28 13:25             ` Lars-Peter Clausen
2021-11-27 15:20       ` Jonathan Cameron
2021-11-27 15:20         ` Jonathan Cameron
2021-11-15 14:22 ` [PATCH 12/15] iio: buffer-dmaengine: Support new DMABUF based userspace API Paul Cercueil
2021-11-15 14:22   ` Paul Cercueil
2021-11-15 14:22   ` [PATCH 13/15] iio: core: Add support for cyclic buffers Paul Cercueil
2021-11-15 14:22     ` Paul Cercueil
2021-11-16  9:50     ` Alexandru Ardelean
2021-11-16  9:50       ` Alexandru Ardelean
2021-11-15 14:22   ` [PATCH 14/15] iio: buffer-dmaengine: " Paul Cercueil
2021-11-15 14:22     ` Paul Cercueil
2021-11-16  9:50     ` Alexandru Ardelean
2021-11-16  9:50       ` Alexandru Ardelean
2021-11-15 14:22   ` [PATCH 15/15] Documentation: iio: Document high-speed DMABUF based API Paul Cercueil
2021-11-15 14:22     ` Paul Cercueil
2021-11-21 15:10     ` Jonathan Cameron
2021-11-21 15:10       ` Jonathan Cameron
2021-11-21 17:46       ` Paul Cercueil
2021-11-21 17:46         ` Paul Cercueil
2021-11-15 14:37 ` [PATCH 00/15] iio: buffer-dma: write() and new " Daniel Vetter
2021-11-15 14:37   ` Daniel Vetter
2021-11-15 14:57   ` Paul Cercueil
2021-11-15 14:57     ` Paul Cercueil
2021-11-16 16:02     ` Daniel Vetter
2021-11-16 16:02       ` Daniel Vetter
2021-11-16 16:31       ` Laurent Pinchart
2021-11-16 16:31         ` Laurent Pinchart
2021-11-17  8:48         ` Christian König
2021-11-17  8:48           ` Christian König
2021-11-17 12:50       ` Paul Cercueil
2021-11-17 12:50         ` Paul Cercueil
2021-11-17 13:42         ` Hennerich, Michael
2021-11-17 13:42           ` Hennerich, Michael
2021-11-21 13:57 ` Jonathan Cameron
2021-11-21 13:57   ` Jonathan Cameron

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=332d001d-8b5a-bba2-c490-ed2e5efd0b1d@metafoo.de \
    --to=lars@metafoo.de \
    --cc=Michael.Hennerich@analog.com \
    --cc=ardeleanalex@gmail.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jic23@kernel.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=paul@crapouillou.net \
    --cc=sumit.semwal@linaro.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.