[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4e6405fa-2939-20ea-dcec-5041c5e1f2f3@huawei.com>
Date: Thu, 19 May 2022 12:20:10 +0800
From: "Ziyang Xuan (William)" <william.xuanziyang@...wei.com>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
CC: <chandrashekar.devegowda@...el.com>, <linuxwwan@...el.com>,
<chiranjeevi.rapolu@...ux.intel.com>, <haijun.liu@...iatek.com>,
<m.chetan.kumar@...ux.intel.com>,
<ricardo.martinez@...ux.intel.com>, <loic.poulain@...aro.org>,
<ryazanov.s.a@...il.com>, <johannes@...solutions.net>,
<davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
<pabeni@...hat.com>, Netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next v2] net: wwan: t7xx: fix GFP_KERNEL usage in
spin_lock context
> On Tue, 17 May 2022, Ziyang Xuan wrote:
>
>> t7xx_cldma_clear_rxq() call t7xx_cldma_alloc_and_map_skb() in spin_lock
>> context, But __dev_alloc_skb() in t7xx_cldma_alloc_and_map_skb() uses
>> GFP_KERNEL, that will introduce scheduling factor in spin_lock context.
>>
>> Because t7xx_cldma_clear_rxq() is called after stopping CLDMA, so we can
>> remove the spin_lock from t7xx_cldma_clear_rxq().
>>
>
> Perhaps Suggested-by: ... would have been appropriate too.
Yes,I will send the v3 patch.
>
>> Fixes: 39d439047f1d ("net: wwan: t7xx: Add control DMA interface")
>> Signed-off-by: Ziyang Xuan <william.xuanziyang@...wei.com>
>
Powered by blists - more mailing lists