linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, Hugo Mills <hugo@carfax.org.uk>,
	sri <toyours_sridhar@yahoo.co.in>,
	linux-btrfs@vger.kernel.org
Subject: Re: how many chunk trees and extent trees present
Date: Fri, 4 Mar 2016 10:58:15 +0800	[thread overview]
Message-ID: <56D8F9C7.70609@oracle.com> (raw)
In-Reply-To: <20150417172928.GT25622@twin.jikos.cz>



On 04/18/2015 01:29 AM, David Sterba wrote:
> On Fri, Apr 17, 2015 at 09:19:11AM +0000, Hugo Mills wrote:
>>> In, some article i read that future there will be more chunk tree/ extent
>>> tree for single btrfs. Is this true.
>>
>>     I recall, many moons ago, Chris saying that there probably wouldn't
>> be.
>
> More extent trees tied to a set of fs trees/subvolumes would be very
> useful for certain usecases *cough*encryption*cough*.

  I didn't understand in full what's the idea here, but let met try..
  would it not defeat the purpose of encryption which is not to let
  disk have the un-encrypted data ? Looks like I am missing something
  here.

Thanks, Anand

  parent reply	other threads:[~2016-03-04  2:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17  6:24 how many chunk trees and extent trees present sri
2015-04-17  9:19 ` Hugo Mills
2015-04-17  9:56   ` sri
2016-02-25 12:16     ` sri
2016-02-26  1:21       ` Qu Wenruo
2015-04-17 17:29   ` David Sterba
2016-02-26  1:29     ` Qu Wenruo
2016-03-03 10:02       ` David Sterba
2016-03-04  2:58     ` Anand Jain [this message]
2016-03-04  9:26       ` David Sterba

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=56D8F9C7.70609@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=toyours_sridhar@yahoo.co.in \
    /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;
as well as URLs for NNTP newsgroup(s).