All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Robert.Heinzmann@deutschepost.de
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Question on Disk Layout (Stacking supported ?)
Date: Thu, 10 Mar 2011 20:09:08 +0100	[thread overview]
Message-ID: <4D7921D4.9080907@redhat.com> (raw)
In-Reply-To: <DA0E1B0401643E4E9750810C61C8697F0496AE2B@ISS-EXM1005.deutschepost.dpwn.com>

On 03/10/2011 07:06 PM, Robert.Heinzmann@deutschepost.de wrote:

> Do you see any problems (from the dm_crypt side) with this setup in
> terms of deadlocks, or unsupported stacking  or is this a "supposed
> to work" configuration ?

Stacking should work without problems. Just when online resizing
you need additional step when resizing crypt device
(cryptsetup resize <dev> is for online resize. Or just activate/
deactivate and it loads new size.)

I depends on your preference if you want use LVM over LUKS or vice versa,
both works.

Basically stacking is design feature of device-mapper.

> I know that device mapper always causes performance penalty because
> of missing barrier support (earlier Kernels) and I/O splitting in 4k
> units, however I have a BBU, so not a problem really and performance
> penalty is allowed.

Barrier (or flush) is fully supported in recent kernels, even for dmcrypt.
Split to 4k unit is also solved long time ago, dmcrypt provides
io merge functionality so even when stacking devices it uses
"ideal" io size - depends on underlying device and io pattern.

So it depends on which distro and kernel you are using.
(I guess you are using RHEL5 clone, even there it can be configure
efficiently. In fact many users have very similar configuration like you
described.)

Milan

  parent reply	other threads:[~2011-03-10 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 18:06 [dm-crypt] Question on Disk Layout (Stacking supported ?) Robert.Heinzmann
2011-03-10 18:57 ` Arno Wagner
2011-03-10 19:09 ` Milan Broz [this message]
2011-03-11  8:34   ` Robert.Heinzmann

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=4D7921D4.9080907@redhat.com \
    --to=mbroz@redhat.com \
    --cc=Robert.Heinzmann@deutschepost.de \
    --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.