From: David Sterba <dsterba@suse.cz>
To: David Disseldorp <ddiss@suse.de>
Cc: Ceriel Jacobs <linux-ide@crashplan.pro>, linux-btrfs@vger.kernel.org
Subject: Re: Project idea: reduce boot time/RAM usage: option to disable/delay raid6_pq and xor kmod
Date: Tue, 2 Jan 2018 18:55:04 +0100 [thread overview]
Message-ID: <20180102175504.GY3553@twin.jikos.cz> (raw)
In-Reply-To: <20171228211807.60f115f4@suse.de>
On Thu, Dec 28, 2017 at 09:18:07PM +0100, David Disseldorp wrote:
> On Sun, 24 Dec 2017 13:31:40 +0100, Ceriel Jacobs wrote:
>
> > Saving:
> > 1. ± 0.4 seconds of boot time (10% of boot until root)
> > 2. ± 150k of RAM
> > 3. ± 75k of disk space
>
> Thanks for bringing this up - I'm also particularly frustrated by the
> boot delay caused by the raid6 algorithm benchmark (1).
>
> > New kernel command-line parameters?
> > a.) disable, like:
> > - btrfs=noraid6_pq
> > - btrfs=noraid (=no xor at all)
> > b.) delay raid6_pq and xor module loading, for cases where root mount
> > doesn't need raid6_pq and/or xor.
>
> c) It might not help with (2) or (3), but I'd be happy with an option to
> preselect the raid6 algorithm, so that the benchmark didn't run on each
> boot.
The preselection looks like the least intrusive option.
Another other option is loading the modules on demand (either explicitly
eg. inside the first mount or implicitly on the first use of the loaded
module), which might be tricky.
The crc32c functions are loaded through the crypto API, and not as a
direct module, but still initialized in the btfs module initialization
itself.
prev parent reply other threads:[~2018-01-02 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 12:31 Project idea: reduce boot time/RAM usage: option to disable/delay raid6_pq and xor kmod Ceriel Jacobs
2017-12-28 20:18 ` David Disseldorp
2018-01-02 17:55 ` David Sterba [this message]
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=20180102175504.GY3553@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=ddiss@suse.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ide@crashplan.pro \
/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).