linux-kernel - [PATCH 0/2] Push the asynchronous function call concept a little further

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-next>] [day] [month] [year] [list]

Date:	Tue, 6 Jan 2009 13:06:28 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	linux-kernel@...r.kernel.org
Cc:	linux-fs@...r.kernel.org, torvalds@...ux-foundation.org
Subject: [PATCH 0/2] Push the asynchronous function call concept a little
 further

Hi,

the 2 patches in this series try to push the asynchronous function call
concept a little further;

the first patch allows for creating multiple queues so that you can do
synchronization on your own queue without creating congestion in the
one global queue (for example, as used in the 2nd patch, a per
superblock queue).

the second patch uses a per superblock queue to make the last part of
file deletion (the actual removal of the file content from disk)
using the async function call concept.
The cut is done after the inode is removed from the VFS (and where the
code can and does sleep), but before calling into the filesystem to do 
the actual removal. The locking etc around this should be safe due to
the sleep-ability and the fact that the inode is already out of the VFS
namespaces (eg it's in I_FREEING).

On my testbox, rm -rf of a kernel tree went from 11.6 to 8.6 seconds
with this; with smaller rm's I expect the gain to be more (to the point
where applications that only occasionally delete files no longer will
stutter around this as much).

-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/