From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] [PATCH] Speed up keyfile reading
Date: Sat, 12 Aug 2017 22:26:09 +0200 [thread overview]
Message-ID: <20170812202609.GC21364@tansi.org> (raw)
In-Reply-To: <20170812194919.GR31146@yeono.dyn.pirkum.se>
On Sat, Aug 12, 2017 at 21:49:19 CEST, Michael Kjörling wrote:
> On 12 Aug 2017 21:37 +0200, from gmazyland@gmail.com (Milan Broz):
> > How big is that keyfile? (And what is underlying storage?)
> > Just wonder why it is so slow...
> >
> > Anyway, patches look good, I will commit it later.
>
> FWIW, I concur with both. The patch looks fine to me, but it's weird
> that it should be needed in the first place.
Indeed. Usually, the read-ahead of the VFS system should
make this a still pretty fast operation. Is this on some
special filesystem, like FLASH-filesystem on a really slow
device? Or is this a really, really large keyfile?
Regards,
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2017-08-12 20:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 18:26 [dm-crypt] [PATCH] Speed up keyfile reading angelomariafederichini191269
2017-08-12 19:37 ` Milan Broz
2017-08-12 19:49 ` Michael Kjörling
2017-08-12 20:26 ` Arno Wagner [this message]
2017-08-13 12:34 ` angelomariafederichini191269
2017-08-13 13:16 ` Michael Kjörling
2017-08-13 13:31 ` Michael Kjörling
2017-08-13 15:33 ` Richard Z
2017-08-13 16:56 ` Michael Kjörling
2017-08-15 9:52 ` Milan Broz
2017-08-19 6:31 ` angelomariafederichini191269
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=20170812202609.GC21364@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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 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.