On 2/24/2018 5:27 AM, Miguel Ojeda wrote:
On Wed, Feb 21, 2018 at 5:56 AM, Asutosh Das wrote:
From: Vijay Viswanath
UFS driver can receive a request during memory reclaim by kswapd.
So when ufs driver puts the ungate work in queue, and if
On 2/24/2018 5:27 AM, Miguel Ojeda wrote:
On Wed, Feb 21, 2018 at 5:56 AM, Asutosh Das wrote:
From: Vijay Viswanath
UFS driver can receive a request during memory reclaim by kswapd.
So when ufs driver puts the ungate work in queue, and if there are no
idle workers, kthreadd is invoked to
On Wed, Feb 21, 2018 at 5:56 AM, Asutosh Das wrote:
> From: Vijay Viswanath
>
> UFS driver can receive a request during memory reclaim by kswapd.
> So when ufs driver puts the ungate work in queue, and if there are no
> idle workers, kthreadd is
On Wed, Feb 21, 2018 at 5:56 AM, Asutosh Das wrote:
> From: Vijay Viswanath
>
> UFS driver can receive a request during memory reclaim by kswapd.
> So when ufs driver puts the ungate work in queue, and if there are no
> idle workers, kthreadd is invoked to create a new kworker. Since
> kswapd
From: Vijay Viswanath
UFS driver can receive a request during memory reclaim by kswapd.
So when ufs driver puts the ungate work in queue, and if there are no
idle workers, kthreadd is invoked to create a new kworker. Since
kswapd task holds a mutex which kthreadd also
From: Vijay Viswanath
UFS driver can receive a request during memory reclaim by kswapd.
So when ufs driver puts the ungate work in queue, and if there are no
idle workers, kthreadd is invoked to create a new kworker. Since
kswapd task holds a mutex which kthreadd also needs, this can cause
a
6 matches
Mail list logo