Re: POHMELFS high performance network filesystem. Transactions, failover, performance.
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 13 May 2008 23:33:41 -0700
On Tue, 13 May 2008 21:45:24 +0400 Evgeniy Polyakov <johnpol@xxxxxxxxxxx> wrote:
I'm please to announce POHMEL high performance network filesystem.
If any thread takes more than one kmap() at a time, it is deadlockable.
Because there is a finite pool of kmaps. Everyone can end up holding
one or more kmaps, then waiting for someone else to release one.
Duplicating page_waitqueue() is bad. Exporting it is probably bad too.
Better would be to help us work out why the core kernel infrastructure is
unsuitable, then make it suitable.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: POHMELFS high performance network filesystem. Transactions, failover, performance.
- From: Evgeniy Polyakov
- Re: POHMELFS high performance network filesystem. Transactions, failover, performance.
- References:
- POHMELFS high performance network filesystem. Transactions, failover, performance.
- From: Evgeniy Polyakov
- POHMELFS high performance network filesystem. Transactions, failover, performance.
- Prev by Date: Re: [PATCH] common implementation of iterative div/mod
- Next by Date: Re: [PATCH 0/2]: Add sparc64 ftrace support.
- Previous by thread: Re: POHMELFS high performance network filesystem. Transactions, failover, performance.
- Next by thread: Re: POHMELFS high performance network filesystem. Transactions, failover, performance.
- Index(es):
Relevant Pages
|
