On Fri, 2006-12-15 at 08:49 -0500, Trond Myklebust wrote:
> On Thu, 2006-12-14 at 22:35 -0800, Chen, Kenneth W wrote:
> > Chen, Kenneth wrote on Thursday, December 14, 2006 5:59 PM
> > > > It seems utterly insane to have aio_complete() flush a workqueue. That
> > > > function has to be called from
On Thu, 2006-12-14 at 22:35 -0800, Chen, Kenneth W wrote:
> Chen, Kenneth wrote on Thursday, December 14, 2006 5:59 PM
> > > It seems utterly insane to have aio_complete() flush a workqueue. That
> > > function has to be called from a number of different environments,
> > > including non-sleep
On Thu, 2006-12-14 at 22:35 -0800, Chen, Kenneth W wrote:
Chen, Kenneth wrote on Thursday, December 14, 2006 5:59 PM
It seems utterly insane to have aio_complete() flush a workqueue. That
function has to be called from a number of different environments,
including non-sleep tolerant
On Fri, 2006-12-15 at 08:49 -0500, Trond Myklebust wrote:
On Thu, 2006-12-14 at 22:35 -0800, Chen, Kenneth W wrote:
Chen, Kenneth wrote on Thursday, December 14, 2006 5:59 PM
It seems utterly insane to have aio_complete() flush a workqueue. That
function has to be called from a number
Chen, Kenneth wrote on Thursday, December 14, 2006 5:59 PM
> > It seems utterly insane to have aio_complete() flush a workqueue. That
> > function has to be called from a number of different environments,
> > including non-sleep tolerant environments.
> >
> > For instance it means that directIO
Andrew Morton wrote on Thursday, December 14, 2006 5:20 PM
> it's hard to disagree.
>
> Begin forwarded message:
> > On Wed, 2006-12-13 at 08:25 +0100, xb wrote:
> > > Hi all,
> > >
> > > Running some IO stress tests on a 8*ways IA64 platform, we got:
> > > BUG: warning at
Chen, Kenneth wrote on Thursday, December 14, 2006 5:59 PM
It seems utterly insane to have aio_complete() flush a workqueue. That
function has to be called from a number of different environments,
including non-sleep tolerant environments.
For instance it means that directIO on NFS will
Andrew Morton wrote on Thursday, December 14, 2006 5:20 PM
it's hard to disagree.
Begin forwarded message:
On Wed, 2006-12-13 at 08:25 +0100, xb wrote:
Hi all,
Running some IO stress tests on a 8*ways IA64 platform, we got:
BUG: warning at
On Wed, 2006-12-13 at 09:02 +0100, Arjan van de Ven wrote:
> On Wed, 2006-12-13 at 08:25 +0100, xb wrote:
> > Hi all,
> >
> > Running some IO stress tests on a 8*ways IA64 platform, we got:
> > BUG: warning at kernel/mutex.c:132/__mutex_lock_common() message
> > followed by:
> > Unable
On Wed, 2006-12-13 at 08:25 +0100, xb wrote:
> Hi all,
>
> Running some IO stress tests on a 8*ways IA64 platform, we got:
> BUG: warning at kernel/mutex.c:132/__mutex_lock_common() message
> followed by:
> Unable to handle kernel paging request at virtual address
> 00200200
>
On Wed, 2006-12-13 at 08:25 +0100, xb wrote:
Hi all,
Running some IO stress tests on a 8*ways IA64 platform, we got:
BUG: warning at kernel/mutex.c:132/__mutex_lock_common() message
followed by:
Unable to handle kernel paging request at virtual address
00200200
oops
On Wed, 2006-12-13 at 09:02 +0100, Arjan van de Ven wrote:
On Wed, 2006-12-13 at 08:25 +0100, xb wrote:
Hi all,
Running some IO stress tests on a 8*ways IA64 platform, we got:
BUG: warning at kernel/mutex.c:132/__mutex_lock_common() message
followed by:
Unable to handle
12 matches
Mail list logo
