mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yunsheng Lin <linyunsheng@huawei.com>
To: Jason Wang <jasowang@redhat.com>, <davem@davemloft.net>,
	<kuba@kernel.org>
Cc: <will@kernel.org>, <peterz@infradead.org>, <paulmck@kernel.org>,
	<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
	<mst@redhat.com>, <brouer@redhat.com>
Subject: Re: [PATCH net-next] ptr_ring: make __ptr_ring_empty() checking more reliable
Date: Thu, 27 May 2021 14:07:58 +0800	[thread overview]
Message-ID: <25a6b73d-06ec-fe07-b34c-10fea709e055@huawei.com> (raw)
In-Reply-To: <d2287691-1ef9-d2c4-13f6-2baf7b80d905@redhat.com>

On 2021/5/27 12:57, Jason Wang wrote:
> 
> 在 2021/5/26 下午8:29, Yunsheng Lin 写道:
>> Currently r->queue[] is cleared after r->consumer_head is moved
>> forward, which makes the __ptr_ring_empty() checking called in
>> page_pool_refill_alloc_cache() unreliable if the checking is done
>> after the r->queue clearing and before the consumer_head moving
>> forward.
>>
>> Move the r->queue[] clearing after consumer_head moving forward
>> to make __ptr_ring_empty() checking more reliable.
> 
> 
> If I understand this correctly, this can only happens if you run __ptr_ring_empty() in parallel with ptr_ring_discard_one().

Yes.

> 
> I think those two needs to be serialized. Or did I miss anything?

As the below comment in __ptr_ring_discard_one, if the above is true, I
do not think we need to keep consumer_head valid at all times, right?


	/* Note: we must keep consumer_head valid at all times for __ptr_ring_empty
	 * to work correctly.
	 */

> 
> Thanks
> 
> 
>>
>> Signed-off-by: Yunsheng Lin <linyunsheng@huawei.com>
>> ---
>>   include/linux/ptr_ring.h | 26 +++++++++++++++++---------
>>   1 file changed, 17 insertions(+), 9 deletions(-)
>>
>> diff --git a/include/linux/ptr_ring.h b/include/linux/ptr_ring.h
>> index 808f9d3..f32f052 100644
>> --- a/include/linux/ptr_ring.h
>> +++ b/include/linux/ptr_ring.h
>> @@ -261,8 +261,7 @@ static inline void __ptr_ring_discard_one(struct ptr_ring *r)
>>       /* Note: we must keep consumer_head valid at all times for __ptr_ring_empty
>>        * to work correctly.
>>        */
>> -    int consumer_head = r->consumer_head;
>> -    int head = consumer_head++;
>> +    int consumer_head = r->consumer_head + 1;
>>         /* Once we have processed enough entries invalidate them in
>>        * the ring all at once so producer can reuse their space in the ring.
>> @@ -271,19 +270,28 @@ static inline void __ptr_ring_discard_one(struct ptr_ring *r)
>>        */
>>       if (unlikely(consumer_head - r->consumer_tail >= r->batch ||
>>                consumer_head >= r->size)) {
>> +        int tail = r->consumer_tail;
>> +        int head = consumer_head;
>> +
>> +        if (unlikely(consumer_head >= r->size)) {
>> +            r->consumer_tail = 0;
>> +            WRITE_ONCE(r->consumer_head, 0);
>> +        } else {
>> +            r->consumer_tail = consumer_head;
>> +            WRITE_ONCE(r->consumer_head, consumer_head);
>> +        }
>> +
>>           /* Zero out entries in the reverse order: this way we touch the
>>            * cache line that producer might currently be reading the last;
>>            * producer won't make progress and touch other cache lines
>>            * besides the first one until we write out all entries.
>>            */
>> -        while (likely(head >= r->consumer_tail))
>> -            r->queue[head--] = NULL;
>> -        r->consumer_tail = consumer_head;
>> -    }
>> -    if (unlikely(consumer_head >= r->size)) {
>> -        consumer_head = 0;
>> -        r->consumer_tail = 0;
>> +        while (likely(--head >= tail))
>> +            r->queue[head] = NULL;
>> +
>> +        return;
>>       }
>> +
>>       /* matching READ_ONCE in __ptr_ring_empty for lockless tests */
>>       WRITE_ONCE(r->consumer_head, consumer_head);
>>   }
> 
> 
> .
> 


  reply	other threads:[~2021-05-27  6:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 12:29 Yunsheng Lin
2021-05-27  4:57 ` Jason Wang
2021-05-27  6:07   ` Yunsheng Lin [this message]
2021-05-27  6:53     ` Jason Wang
2021-05-27  7:21       ` Yunsheng Lin
2021-05-27  8:05         ` Jason Wang
2021-05-27  9:03           ` Yunsheng Lin
2021-05-28  1:31             ` Jason Wang
2021-05-28  2:26               ` Yunsheng Lin
2021-05-28  2:29                 ` Jason Wang

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=25a6b73d-06ec-fe07-b34c-10fea709e055@huawei.com \
    --to=linyunsheng@huawei.com \
    --cc=brouer@redhat.com \
    --cc=davem@davemloft.net \
    --cc=jasowang@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=will@kernel.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

all inboxes | Powered by JetHome®