Roland Dreier wrote:
Thanks for the explanation...
> But basically, with CONFIG_PREEMPT_RT enabled, the lock points, such as
> aqcuiring a spinlock, potentially become places where the current task
> may be context switched out / preempted.
>
> Therefore, when a call is made to lock a
Thanks for the explanation...
> But basically, with CONFIG_PREEMPT_RT enabled, the lock points, such as
> aqcuiring a spinlock, potentially become places where the current task
> may be context switched out / preempted.
>
> Therefore, when a call is made to lock a spinlock for example, the
> Subject: Re: [ofa-general] [PATCH] [WORKAROUND] CONFIG_PREEMPT_RT and
ib_umad_close() issue
> From: Roland Dreier <[EMAIL PROTECTED]>
> Date: Mon, 17 Sep 2007 08:56:01 -0700
> To: John Blackwood <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED], linux-kernel@vger.kernel.or
On Mon, 2007-09-17 at 08:56 -0700, Roland Dreier wrote:
> > When using OFED-1.2.5 based infiniband kernel modules on 2.6.22 based
> > kernels with the Ingo Molnar CONFIG_PREEMPT_RT applied, then commands
> > such as ibnetdiscvoer, smpquery, sminfo, etc. will hang. The problem
> > is with the
> When using OFED-1.2.5 based infiniband kernel modules on 2.6.22 based
> kernels with the Ingo Molnar CONFIG_PREEMPT_RT applied, then commands
> such as ibnetdiscvoer, smpquery, sminfo, etc. will hang. The problem
> is with the downgrade_write() rw semaphore usage in the
> ib_umad_close()
When using OFED-1.2.5 based infiniband kernel modules on 2.6.22 based
kernels with the Ingo Molnar CONFIG_PREEMPT_RT applied, then commands
such as ibnetdiscvoer, smpquery, sminfo, etc. will hang. The problem
is with the downgrade_write() rw semaphore usage in the
ib_umad_close()
On Mon, 2007-09-17 at 08:56 -0700, Roland Dreier wrote:
When using OFED-1.2.5 based infiniband kernel modules on 2.6.22 based
kernels with the Ingo Molnar CONFIG_PREEMPT_RT applied, then commands
such as ibnetdiscvoer, smpquery, sminfo, etc. will hang. The problem
is with the
Subject: Re: [ofa-general] [PATCH] [WORKAROUND] CONFIG_PREEMPT_RT and
ib_umad_close() issue
From: Roland Dreier [EMAIL PROTECTED]
Date: Mon, 17 Sep 2007 08:56:01 -0700
To: John Blackwood [EMAIL PROTECTED]
CC: [EMAIL PROTECTED], linux-kernel@vger.kernel.org,
[EMAIL PROTECTED], Sven-Thorsten
Thanks for the explanation...
But basically, with CONFIG_PREEMPT_RT enabled, the lock points, such as
aqcuiring a spinlock, potentially become places where the current task
may be context switched out / preempted.
Therefore, when a call is made to lock a spinlock for example, the
Roland Dreier wrote:
Thanks for the explanation...
But basically, with CONFIG_PREEMPT_RT enabled, the lock points, such as
aqcuiring a spinlock, potentially become places where the current task
may be context switched out / preempted.
Therefore, when a call is made to lock a spinlock
10 matches
Mail list logo
