Re: [Patch 06/18] fs/logfs/compr.c

On Mon, 2007-06-04 at 10:54 +0200, Jörn Engel wrote:
> There is no particular reason.  '3' should be a reasonable value for
> most people.  If actual users want to change this value, I can make it
> a mount option as well.  Right now I'm just lazy and doubt the merits.

I think you probably made the right choice. If you're compressing small
chunks at a time, increasing the amount of history which the compressor
will keep really doesn't buy you much.

-- 
dwmw2

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • LogFS take four
    • From: Jörn Engel <[email protected]>
  • [Patch 06/18] fs/logfs/compr.c
    • From: Jörn Engel <[email protected]>
  • Re: [Patch 06/18] fs/logfs/compr.c
    • From: Arnd Bergmann <[email protected]>
  • Re: [Patch 06/18] fs/logfs/compr.c
    • From: Jörn Engel <[email protected]>

• Prev by Date: Re: slow open() calls and o_nonblock
• Next by Date: Re: 2.6.22-rc[23]: blinking capslock led, stuck keys?
• Previous by thread: Re: [Patch 06/18] fs/logfs/compr.c
• Next by thread: [Patch 07/18] fs/logfs/dir.c
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]