From: Arjan van de Ven <arjan@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: linux-fs@vger.kernel.org, torvalds@linux-foundation.org
Subject: [PATCH 0/2] Push the asynchronous function call concept a little further
Date: Tue, 6 Jan 2009 13:06:28 -0800 [thread overview]
Message-ID: <20090106130628.59d63bee@infradead.org> (raw)
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
next reply other threads:[~2009-01-06 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 21:06 Arjan van de Ven [this message]
2009-01-06 21:07 ` [PATCH 1/2] async: allow for multiple independent synchronization domains Arjan van de Ven
2009-01-06 21:08 ` [PATCH 2/2] async: make the final inode deletion an asynchronous event Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090106130628.59d63bee@infradead.org \
--to=arjan@infradead.org \
--cc=linux-fs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome