Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
To:     <agross@kernel.org>, <andersson@kernel.org>,
        <konrad.dybcio@linaro.org>, <mathieu.poirier@linaro.org>,
        <linux-arm-msm@vger.kernel.org>,
        <linux-remoteproc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
CC:     <quic_srichara@quicinc.com>, <quic_sjaganat@quicinc.com>,
        <quic_kathirav@quicinc.com>, <quic_anusha@quicinc.com>,
        <quic_varada@quicinc.com>
Subject: [PATCH 0/2] change glink work queue type
Date:   Wed, 7 Jun 2023 17:47:29 +0530
Message-ID: <20230607121731.26958-1-quic_mmanikan@quicinc.com>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

Since rx & intent worker threads are bound
to kernel global workqueue, it takes more
time to execute. If these worker threads
are not executed within stipulated duration
QDSP6 will OOM and glink client drivers get
timeout error.

This series will change work queue type to
UNBOUND work queue to ensure worker thread
execute as early as possible.

It's verified on IPQ807x.

Manikanta Mylavarapu (2):
  rpmsg: glink: change rx work queue type
  rpmsg: glink: change intent work queue type

 drivers/rpmsg/qcom_glink_native.c | 23 +++++++++++++++++++++--
 1 file changed, 21 insertions(+), 2 deletions(-)


base-commit: abbd8bb42915d9ed06df11b430bf4ecb3d8ac5ad
--
2.17.1