btrfs: use add_to_page_cache_lru, use __page_cache_alloc
Pagecache pages should be allocated with __page_cache_alloc, so they
obey pagecache memory policies.
add_to_page_cache_lru is exported, so it should be used. Benefits over
using a private pagevec: neater code, 128 bytes fewer stack used, pe
On Tuesday 16 March 2010 10:21:43 David Brown wrote:
> Hi,
>
> I was wondering if there has been any thought or progress in
> content-based storage for btrfs beyond the suggestion in the "Project
> ideas" wiki page?
>
> The basic idea, as I understand it, is that a longer data extent
> checksum i
Some years ago I was searching for that kind of functionality and found
an experimental ext3 patch to allow the so-called COW-links:
http://lwn.net/Articles/76616/
There was a discussion later on LWN http://lwn.net/Articles/77972/
an approach like COW-links would break POSIX standards.
I am no
On Mon, Mar 15, 2010 at 03:18:07PM -0400, Chris Mason wrote:
> Hello everyone,
>
> The master branch of the btrfs unstable tree has a collection of fixes
> and features:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git master
I've updated the master tree with 3 small fi
Hi Chris
On Monday 15 March 2010, Chris Mason wrote:
> On Fri, Mar 12, 2010 at 07:30:01PM +0100, Goffredo Baroncelli wrote:
> > On Friday 12 March 2010, Pat Patterson wrote:
> > > Are there any plans to implement something akin to ZFS send/recv, to
> > > be able to create a stream representation o
Hi,
I was wondering if there has been any thought or progress in
content-based storage for btrfs beyond the suggestion in the "Project
ideas" wiki page?
The basic idea, as I understand it, is that a longer data extent
checksum is used (long enough to make collisions unrealistic), and merge
