From: Kalle Valo <kvalo@codeaurora.org>
To: Bhaumik Bhatt <bbhatt@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-arm-msm@vger.kernel.org,
hemantk@codeaurora.org, linux-kernel@vger.kernel.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v5] bus: mhi: core: Add support for processing priority of event ring
Date: Thu, 16 Sep 2021 08:28:50 +0300 [thread overview]
Message-ID: <87bl4t1431.fsf@codeaurora.org> (raw)
In-Reply-To: <9561c5a41e1707d694b1c872fea399de@codeaurora.org> (Bhaumik Bhatt's message of "Wed, 28 Jul 2021 17:06:24 -0700")
Hi Bhaumik,
Bhaumik Bhatt <bbhatt@codeaurora.org> writes:
> On 2021-07-16 11:22 AM, Bhaumik Bhatt wrote:
>> Hi Mani,
>>
>> On 2021-07-16 04:49 AM, Manivannan Sadhasivam wrote:
>>> On Fri, Jun 25, 2021 at 10:22:08AM -0700, Bhaumik Bhatt wrote:
>>>> From: Hemant Kumar <hemantk@codeaurora.org>
>>>>
>>>> Event ring priorities are currently set to 1 and are unused.
>>>> Default processing priority for event rings is set to regular
>>>> tasklet. Controllers can choose to use high priority tasklet
>>>> scheduling for certain event rings critical for processing such
>>>> as ones transporting control information if they wish to avoid
>>>> system scheduling delays for those packets. In order to support
>>>> these use cases, allow controllers to set event ring priority to
>>>> high.
>>>>
>>>
>>> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
>>>
>>> Just curious, what are the event rings you are going to make as high
>>> priority? If you are going to do that for existing controllers, please
>>> submit a patch now itself.
>>>
>>> Thanks,
>>> Mani
>>>
>> Idea for this patch came from 914b72a6948b ("bus: mhi: Wait for M2
>> state during system resume").
>>
>> If WLAN ath11k controller driver wants to avoid the scenario
>> mentioned in
>> the above patch, it will help them to have a high priority for their
>> dedicated
>> control events ring.
>>
>> I would defer to Kalle and others in ath11k, whether or not they are
>> OK to take that route.
>> as an update to priority will just help return from resume faster.
>> It will also depend on system load/reproducibility rate of the
>> scenario.
>>
>> I can provide a patch for them to review/test since I do not have the
>> setup for it.
>>
> Would you like to try this patch out? It basically increases the
> priority
> at which the control events for M0/M1/M3 state changes are handled.
>
> Let me know if you have any questions.
At the moment I'm seriously lagging with patches so I don't really have
any free time. Can some other ath11k developer help here?
--
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@codeaurora.org>
To: Bhaumik Bhatt <bbhatt@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-arm-msm@vger.kernel.org,
hemantk@codeaurora.org, linux-kernel@vger.kernel.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v5] bus: mhi: core: Add support for processing priority of event ring
Date: Thu, 16 Sep 2021 08:28:50 +0300 [thread overview]
Message-ID: <87bl4t1431.fsf@codeaurora.org> (raw)
In-Reply-To: <9561c5a41e1707d694b1c872fea399de@codeaurora.org> (Bhaumik Bhatt's message of "Wed, 28 Jul 2021 17:06:24 -0700")
Hi Bhaumik,
Bhaumik Bhatt <bbhatt@codeaurora.org> writes:
> On 2021-07-16 11:22 AM, Bhaumik Bhatt wrote:
>> Hi Mani,
>>
>> On 2021-07-16 04:49 AM, Manivannan Sadhasivam wrote:
>>> On Fri, Jun 25, 2021 at 10:22:08AM -0700, Bhaumik Bhatt wrote:
>>>> From: Hemant Kumar <hemantk@codeaurora.org>
>>>>
>>>> Event ring priorities are currently set to 1 and are unused.
>>>> Default processing priority for event rings is set to regular
>>>> tasklet. Controllers can choose to use high priority tasklet
>>>> scheduling for certain event rings critical for processing such
>>>> as ones transporting control information if they wish to avoid
>>>> system scheduling delays for those packets. In order to support
>>>> these use cases, allow controllers to set event ring priority to
>>>> high.
>>>>
>>>
>>> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
>>>
>>> Just curious, what are the event rings you are going to make as high
>>> priority? If you are going to do that for existing controllers, please
>>> submit a patch now itself.
>>>
>>> Thanks,
>>> Mani
>>>
>> Idea for this patch came from 914b72a6948b ("bus: mhi: Wait for M2
>> state during system resume").
>>
>> If WLAN ath11k controller driver wants to avoid the scenario
>> mentioned in
>> the above patch, it will help them to have a high priority for their
>> dedicated
>> control events ring.
>>
>> I would defer to Kalle and others in ath11k, whether or not they are
>> OK to take that route.
>> as an update to priority will just help return from resume faster.
>> It will also depend on system load/reproducibility rate of the
>> scenario.
>>
>> I can provide a patch for them to review/test since I do not have the
>> setup for it.
>>
> Would you like to try this patch out? It basically increases the
> priority
> at which the control events for M0/M1/M3 state changes are handled.
>
> Let me know if you have any questions.
At the moment I'm seriously lagging with patches so I don't really have
any free time. Can some other ath11k developer help here?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-09-16 5:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 17:22 [PATCH v5] bus: mhi: core: Add support for processing priority of event ring Bhaumik Bhatt
2021-07-16 11:49 ` Manivannan Sadhasivam
2021-07-16 18:22 ` Bhaumik Bhatt
2021-07-29 0:06 ` Bhaumik Bhatt
2021-07-29 0:06 ` Bhaumik Bhatt
2021-09-16 5:28 ` Kalle Valo [this message]
2021-09-16 5:28 ` 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=87bl4t1431.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=bbhatt@codeaurora.org \
--cc=hemantk@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=manivannan.sadhasivam@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.