From: "Ziyang Xuan (William)" <william.xuanziyang@huawei.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: <chandrashekar.devegowda@intel.com>, <linuxwwan@intel.com>,
<chiranjeevi.rapolu@linux.intel.com>, <haijun.liu@mediatek.com>,
<m.chetan.kumar@linux.intel.com>,
<ricardo.martinez@linux.intel.com>, <loic.poulain@linaro.org>,
<ryazanov.s.a@gmail.com>, <johannes@sipsolutions.net>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2] net: wwan: t7xx: fix GFP_KERNEL usage in spin_lock context
Date: Thu, 19 May 2022 12:20:10 +0800 [thread overview]
Message-ID: <4e6405fa-2939-20ea-dcec-5041c5e1f2f3@huawei.com> (raw)
In-Reply-To: <d04ffa5b-13f6-5f4d-98e4-1a4550d6f69@linux.intel.com>
> 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@huawei.com>
>
prev parent reply other threads:[~2022-05-19 4:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 6:48 [PATCH net-next v2] net: wwan: t7xx: fix GFP_KERNEL usage in spin_lock context Ziyang Xuan
2022-05-17 8:35 ` Sergey Ryazanov
2022-05-17 8:50 ` Loic Poulain
2022-05-18 4:39 ` Ziyang Xuan (William)
2022-05-18 18:09 ` Ilpo Järvinen
2022-05-19 4:20 ` Ziyang Xuan (William) [this message]
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=4e6405fa-2939-20ea-dcec-5041c5e1f2f3@huawei.com \
--to=william.xuanziyang@huawei.com \
--cc=chandrashekar.devegowda@intel.com \
--cc=chiranjeevi.rapolu@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haijun.liu@mediatek.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linuxwwan@intel.com \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ricardo.martinez@linux.intel.com \
--cc=ryazanov.s.a@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).