linux-kernel - Re: [RFC][PATCH] 9p: add readahead support for loose mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070916221606.065e449f@lappy>
Date:	Sun, 16 Sep 2007 22:16:06 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Eric Van Hensbergen <ericvh@...il.com>,
	v9fs-developer@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [RFC][PATCH] 9p: add readahead support for loose mode

On Sat, 15 Sep 2007 03:41:26 -0700 Andrew Morton
<akpm@...ux-foundation.org> wrote:

> eww, kmap.  Large amounts of them, apparently.
> 
> Be aware that kmap is a) slow and b) deadlockable.  The latter happens when
> multiple tasks want to take more than one kmap simultaneously: they all
> wait for someone else to release one.  Your code here seems especially
> vulnerable to this.
> 
> Nick had a kmap-speedup patchset a while back which addressed a) but I
> don't know if it addressed the deadlock.  But that patch seemed to die.

That would've been me.

What I did to address b) is to pre-allocate each kmap user a second
kmap slot. Of course this isn't water-tight either.

These patches are part of -rt, I could respin against mainline if there
is interest.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/