From: ludo@gnu.org (Ludovic Courtès)
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: GRUB LUKS support is slow?
Date: Mon, 18 Dec 2017 10:39:19 +0100 [thread overview]
Message-ID: <87k1xkwf20.fsf@gnu.org> (raw)
In-Reply-To: <323370e6-660e-0e7e-065b-39a7346c22cc@tobias.gr> (Tobias Geerinckx-Rice's message of "Sat, 16 Dec 2017 02:10:24 +0100")
Hi,
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> Adam Van Ymeren wrote on 16/12/17 at 00:25:
>> On December 15, 2017 5:53:15 PM EST, Mark H Weaver <mhw@netris.org>
>> wrote:
>>> ludo@gnu.org (Ludovic Courtès) writes:
>>>
>>>> I have an encrypted root. When GRUB asks me for my passphrase,
>>>> it takes 5–10 seconds after I hit enter before it displays the
>>>> menu; then, once I've selected an entry, it takes another 5 seconds
>>>> or so to boot.
>>>>
>>>> It’s always been this way for me (that’s on UEFI), but I’m
>>>> sufficiently annoyed to write this message today. :-)
>>>>
>>>> Are others experiencing this as well? Any hints?
>>>
>>> I also use a LUKS-encrypted root partition, and the same thing
>>> happens to me. I would guess that the cryptographic operations in
>>> GRUB are not well optimized, but I haven't looked closely.
>>>
>>> Mark
>>
>> Even unoptimized 5-10s seems pretty long. It's not like it has a
>> lot of data to process.
>
> Alas, you'd be wrong :-)
What’s also “reassuring” is that the searching for “grub luks slow”
suggests that the whole world is booting slowly, not just GuixSD users.
:-)
Ludo’.
next prev parent reply other threads:[~2017-12-18 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 22:04 GRUB LUKS support is slow? Ludovic Courtès
2017-12-15 22:53 ` Mark H Weaver
2017-12-15 23:25 ` Adam Van Ymeren
2017-12-16 1:10 ` Tobias Geerinckx-Rice
2017-12-16 2:29 ` Adam Van Ymeren
2017-12-18 9:38 ` Ludovic Courtès
2017-12-18 9:39 ` Ludovic Courtès [this message]
2017-12-18 21:28 ` Tobias Geerinckx-Rice
2017-12-16 1:14 ` Clément Lassieur
2017-12-16 8:10 ` Chris Marusich
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=87k1xkwf20.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.