From: Tomasz Torcz <tomek@pipebreaker.pl>
To: linux-btrfs@vger.kernel.org
Subject: Re: exploit preload daemon to defragment most needed files
Date: Sun, 5 May 2013 15:57:09 +0200 [thread overview]
Message-ID: <20130505135708.GA24548@mother.pipebreaker.pl> (raw)
In-Reply-To: <05mh5a-iqe.ln1@hurikhan.ath.cx>
On Sun, May 05, 2013 at 11:42:24AM +0200, Kai Krakow wrote:
> Hey list,
>
> Although this is about the preload daemon, my intended audience for this
> matter is the btrfs community. So I'm posting this here.
>
> I've created a small script here[1] to read the preload daemon state file
> and use this to run the btrfs defragmenter/compressor on these files. The
> idea was to have some proof-of-concept to maybe integrate defragmentation
> capabilities directly into preload.
In similar spirit, systemd's readhead defrag files on btrfs. Here's the commit:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=746f89063666be8c4d538271c646585ac4fc4353
--
Tomasz Torcz "Never underestimate the bandwidth of a station
xmpp: zdzichubg@chrome.pl wagon filled with backup tapes." -- Jim Gray
next prev parent reply other threads:[~2013-05-05 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-05 9:42 exploit preload daemon to defragment most needed files Kai Krakow
2013-05-05 13:57 ` Tomasz Torcz [this message]
2013-05-05 16:21 ` Kai Krakow
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=20130505135708.GA24548@mother.pipebreaker.pl \
--to=tomek@pipebreaker.pl \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).