linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhihui Zhang <zzhsuny@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: idea about internal fragmentation in Btrfs
Date: Sun, 20 Jun 2010 04:20:54 +0800	[thread overview]
Message-ID: <AANLkTikSD70wX4eBi6GZyOSqL478dmT8_eEmYzz9zzk9@mail.gmail.com> (raw)
In-Reply-To: <87k4pvo16d.fsf@basil.nowhere.org>

Makes perfect sense. No wonder some btrfs folks used to work on
reiserfs/4. I hope a solution can be or has been found.

On Sat, Jun 19, 2010 at 4:51 PM, Andi Kleen <andi@firstfloor.org> wrote=
:
> Zhihui Zhang <zzhsuny@gmail.com> writes:
>
>> I wish Btrfs well, so I would venture an idea for this specific case
>> mentioned by Edward Shishkin today.
>>
>> Everyone knows that B-tree has internal and leaf nodes. =A0Can we ma=
ke
>> the root as the leaf? =A0In other words, if you
>> create a 2K file, the B-tree will have only one node, which is both
>> the root and the leaf. Of course, you need some flag to
>> say this is a "degenerated" form of B-tree. Please cc me if you want
>> my response.
>
> You need to copy linux-btrfs to reach btrfs developers.
> Ccs added
>
> The problem with your idea is that on btrfs there's only
> a single tree for the whole fs (or whole snapshot rather)
> So it would only work for a single file because there's
> only a single root.
>
> -Andi
> --
> ak@linux.intel.com -- Speaking for myself only.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-06-19 20:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTilWguh4IrDHVgtTxjoiAeSy23SK_M1dWapgvSDt@mail.gmail.com>
2010-06-19  8:51 ` idea about internal fragmentation in Btrfs Andi Kleen
2010-06-19 20:20   ` Zhihui Zhang [this message]

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=AANLkTikSD70wX4eBi6GZyOSqL478dmT8_eEmYzz9zzk9@mail.gmail.com \
    --to=zzhsuny@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@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 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).