All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: Re: xfs over thin provisioning talk
Date: Tue, 3 Dec 2013 22:23:51 -0500	[thread overview]
Message-ID: <20131204032351.GC15658@thunk.org> (raw)
In-Reply-To: <20131202165611.GA23816@orion.maiolino.org>

On Mon, Dec 02, 2013 at 02:56:12PM -0200, Carlos Maiolino wrote:
> Hi guys,
> 
> Lukas told me that some guys here might be interested in a talk I did at LPC
> 2013 about XFS using dm-thin module.
> 
> For those interested, the slides can be downloaded here:
> http://people.redhat.com/~cmaiolin/talks/XFS-dmthin.pdf

Hi Carlos,

Thanks for sending these slides.  They are very interesting indeed.

Lukas mentioned that you had run some tests using ext4 and it didn't
do well at all using dm-thin?  Given that we're not doing proper raid
strip alignment in our allocation decisions, that's not too
surprising, but it would be useful if there are other things that we
should do in order to do a better job working with dm-thin drives.

One other question --- in your conclusion you say:

   Bypassing block zeroing while provisioning blocks adds a significant
   boost to the dm-thin performance, but, it can induce a security
   breach, at the risk of exposing stale data

This might be true if you are directly giving dm-thin volumes to
mutually suspicious VM's with different trust boundaries.  But if you
trust the file system, and the dm-thin devices are mediated by the a
file system running in the same context as the dm-thin volumes, there
wouldn't be any security issue, correct?

Cheers,

					- Ted

  reply	other threads:[~2013-12-04  3:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02 16:56 xfs over thin provisioning talk Carlos Maiolino
2013-12-04  3:23 ` Theodore Ts'o [this message]
2013-12-06 12:45   ` Carlos Maiolino

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=20131204032351.GC15658@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.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 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.