All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/5] btrfs: Add lzo compression support
Date: Tue, 26 Oct 2010 10:34:30 +0800	[thread overview]
Message-ID: <4CC63E36.8050105@cn.fujitsu.com> (raw)
In-Reply-To: <20101026021341.GW18818@think>

Chris Mason wrote:
> On Mon, Oct 25, 2010 at 03:11:22PM +0800, Li Zefan wrote:
>> Lzo is a much faster compression algorithm than gzib, so would allow
>> more users to enable transparent compression, and some users can
>> choose from compression ratio and compression speed.
> 
> This is also much smaller than I expected, really nice.  It looks like
> older kernels won't properly deal (nicely give EIO) with lzo compressed
> files?
> 
> We can add compatbits to deal with that if it is the case.
> 

I forgot compatibility issue with older kernels..

Though I didn't test older kernels, I don't think they can deal with lzo
compressed files properly, at least not for inlined extents, in which
case I think btrfs will just show compressed data to the users.

So yes, an incompat flag is needed.

  reply	other threads:[~2010-10-26  2:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25  7:11 [PATCH 0/5] btrfs: Add lzo compression support Li Zefan
2010-10-25  7:11 ` [PATCH 1/5] btrfs: Fix bugs in zlib workspace Li Zefan
2010-10-25  7:12 ` [PATCH 2/5] btrfs: Allow to add new compression algorithm Li Zefan
2010-10-25  7:12 ` [PATCH 3/5] btrfs: Add lzo compression support Li Zefan
2010-10-25  7:12 ` [PATCH 4/5] btrfs: Allow to specify compress method when defrag Li Zefan
2010-10-25  7:13 ` [PATCH 5/5] btrfs: Extract duplicate decompress code Li Zefan
2010-10-26  2:13 ` [PATCH 0/5] btrfs: Add lzo compression support Chris Mason
2010-10-26  2:34   ` Li Zefan [this message]
2010-11-15 18:55     ` Mitch Harder
2010-11-16  0:57       ` Li Zefan
2010-11-16 18:51         ` Mitch Harder

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=4CC63E36.8050105@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@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.