All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Karthikeyan Kathirvel <quic_kathirve@quicinc.com>
Cc: ath11k@lists.infradead.org,  linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] ath11k: fix destination monitor ring out of sync
Date: Thu, 16 Dec 2021 18:35:59 +0200	[thread overview]
Message-ID: <87o85gbj80.fsf@codeaurora.org> (raw)
In-Reply-To: <1639584090-13751-1-git-send-email-quic_kathirve@quicinc.com> (Karthikeyan Kathirvel's message of "Wed, 15 Dec 2021 21:31:30 +0530")

Karthikeyan Kathirvel <quic_kathirve@quicinc.com> writes:

> More than 20000 PPDU id jumping causing status ring and destination
> ring processing not sync. The status ring is processed and the
> destination ring is not processed. Since destination is not reaped for
> so long, backpressure occurs at the destination ring.
>
> To address this issue update the PPDU id with the latest PPDU, this
> will allow the destination ring to be reaped and will prevent the
> rings from getting out of sync.
>
> Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.4.0.1.r1-00026-QCAHKSWPL_SILICONZ-2
>
> Signed-off-by: Karthikeyan Kathirvel <quic_kathirve@quicinc.com>

Failed to apply:

Applying: ath11k: fix destination monitor ring out of sync
error: sha1 information is lacking or useless (drivers/net/wireless/ath/ath11k/dp.h).
error: could not build fake ancestor

Please rebase on top ath.git master branch. And remember to use --base,
then it's easier for me to fix conflicts.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Karthikeyan Kathirvel <quic_kathirve@quicinc.com>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] ath11k: fix destination monitor ring out of sync
Date: Thu, 16 Dec 2021 18:35:59 +0200	[thread overview]
Message-ID: <87o85gbj80.fsf@codeaurora.org> (raw)
In-Reply-To: <1639584090-13751-1-git-send-email-quic_kathirve@quicinc.com> (Karthikeyan Kathirvel's message of "Wed, 15 Dec 2021 21:31:30 +0530")

Karthikeyan Kathirvel <quic_kathirve@quicinc.com> writes:

> More than 20000 PPDU id jumping causing status ring and destination
> ring processing not sync. The status ring is processed and the
> destination ring is not processed. Since destination is not reaped for
> so long, backpressure occurs at the destination ring.
>
> To address this issue update the PPDU id with the latest PPDU, this
> will allow the destination ring to be reaped and will prevent the
> rings from getting out of sync.
>
> Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.4.0.1.r1-00026-QCAHKSWPL_SILICONZ-2
>
> Signed-off-by: Karthikeyan Kathirvel <quic_kathirve@quicinc.com>

Failed to apply:

Applying: ath11k: fix destination monitor ring out of sync
error: sha1 information is lacking or useless (drivers/net/wireless/ath/ath11k/dp.h).
error: could not build fake ancestor

Please rebase on top ath.git master branch. And remember to use --base,
then it's easier for me to fix conflicts.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2021-12-16 16:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 16:01 [PATCH v3] ath11k: fix destination monitor ring out of sync Karthikeyan Kathirvel
2021-12-15 16:01 ` Karthikeyan Kathirvel
2021-12-16 16:35 ` Kalle Valo [this message]
2021-12-16 16:35   ` Kalle Valo

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=87o85gbj80.fsf@codeaurora.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_kathirve@quicinc.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 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.