On 2013年01月11日 06:38, Andrew Morton wrote:
On Wed, 9 Jan 2013 11:34:19 +0800
Fan Du wrote:
Two rt tasks bind to one CPU core.
The higher priority rt task A preempts a lower priority rt task B which
has already taken the write seq lock, and then the higher priority
rt task A try to acquire
On Wed, 9 Jan 2013 11:34:19 +0800
Fan Du wrote:
> Two rt tasks bind to one CPU core.
>
> The higher priority rt task A preempts a lower priority rt task B which
> has already taken the write seq lock, and then the higher priority
> rt task A try to acquire read seq lock, it's doomed to lockup.
On Wed, 9 Jan 2013 11:34:19 +0800
Fan Du fan...@windriver.com wrote:
Two rt tasks bind to one CPU core.
The higher priority rt task A preempts a lower priority rt task B which
has already taken the write seq lock, and then the higher priority
rt task A try to acquire read seq lock, it's
On 2013年01月11日 06:38, Andrew Morton wrote:
On Wed, 9 Jan 2013 11:34:19 +0800
Fan Dufan...@windriver.com wrote:
Two rt tasks bind to one CPU core.
The higher priority rt task A preempts a lower priority rt task B which
has already taken the write seq lock, and then the higher priority
rt
Two rt tasks bind to one CPU core.
The higher priority rt task A preempts a lower priority rt task B which
has already taken the write seq lock, and then the higher priority
rt task A try to acquire read seq lock, it's doomed to lockup.
rt task A with lower priority: call write
i_size_write
Two rt tasks bind to one CPU core.
The higher priority rt task A preempts a lower priority rt task B which
has already taken the write seq lock, and then the higher priority
rt task A try to acquire read seq lock, it's doomed to lockup.
rt task A with lower priority: call write
i_size_write
6 matches
Mail list logo
