public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Intel Atom: architecture, distcc, crossdev and compile flags
Date: Fri, 14 Dec 2012 23:29:42 +0100	[thread overview]
Message-ID: <20121214222942.GA9413@eisen.lan> (raw)
In-Reply-To: <50C83D7A.5020403@binarywings.net>

[-- Attachment #1: Type: text/plain, Size: 2486 bytes --]

On Wed, Dec 12, 2012 at 09:16:58AM +0100, Florian Philipp wrote:

> >>> * The last thing I’m going to set up is filesystem encryption, at least for ~.
> >>>   I already know/think that AES would be the best choice due to limited CPU
> >>>   power, but what else is there to heed besides key size?
> >>
> >> Nothing, you're good. Hash and key chaining method have negligible
> >> impact. If you stick with an x86_32 userspace I suggest at least using
> >> an x64 kernel so you can use of CRYPTO_AES_X86_64.
> > 
> > That's an interesting idea.
> >> [...] 
> > I haven't done any comparisons of 32/64 crypto yet, I'm just reading
> > docs on Luks (never used it before).

Well now, I did a few comparisons yesterday. Not much---just permutated a few
of the most probable crypto combinations (aes/twofish, cbc/xts, essiv/plain).
I created the LUKS container, opened it and gave it a spin with hdparm -t.

The result was shocking and outrageous; reported throughput w/o encryption was
75 MB/s, which is your typical 5400 rev laptop HDD.  First I was disappointed
when I saw what aes-cbc-essiv gave me on 32 bit: a mere 19 and a bit.  But on
64 bit, it yielded a whopping 34 MB/s.  I had a hunch and booted the 32 bit
system with the 64 bit kernel---and throughput stayed high as expected.

So for the sake of simplicity (and to give it a rest after two weeks of ricing
to the day), I will use the 32 bit userland with a 64 bit kernel.  I will only
need to set up some magic (a multilib crossdev gcc and separate build dirs) so
I can build both kernels with their separate configs from the same source dir.

> I personally see no reason for encrypting root as there is nothing of
> interest in there.

Hm ideed, the only password I have in a plaintext config file are WiFi
passwords vor wpa and vpnc.  For those the symlink solution could be used.
Not needing an initrd is a big incentive. :)

> > On a sidenote, While I was cleaning up unread mails in the ML, I just
> > found your interesting frontswap/zcache trick.

I tried that, too, but for now will keep it disabled---simple copying of big
files was slowed down to 33 MB/s, obviously b/c the cache is constantly being
changed.  It's just not suitable for little Atoms.
-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any Facebook service.

The duration of a minute is relative.
It depends on the side of the toilet door you are standing on.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-12-14 22:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 17:36 [gentoo-user] Intel Atom: architecture, distcc, crossdev and compile flags Frank Steinmetzger
2012-12-11 19:40 ` Norman Invasion
2012-12-11 20:20 ` Florian Philipp
2012-12-12  1:40   ` Frank Steinmetzger
2012-12-12  8:16     ` Florian Philipp
2012-12-12  9:40       ` Neil Bothwick
2012-12-12 17:41         ` Florian Philipp
2012-12-13  8:06           ` Neil Bothwick
2012-12-14 22:29       ` Frank Steinmetzger [this message]
2012-12-13 18:24     ` Volker Armin Hemmann
2012-12-11 20:23 ` Joseph
2012-12-12  8:32 ` Walter Dnes

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=20121214222942.GA9413@eisen.lan \
    --to=warp_7@gmx.de \
    --cc=gentoo-user@lists.gentoo.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