Valerie Henson wrote:
On Fri, Jun 29, 2007 at 06:07:25PM -0400, Mike Waychison wrote:
Relying on (a tweaked) reservations code is also somewhat limitting at
this stage given that reservations are lost on close(fd). Unless we
change the lifetime of the reservations (maybe for the lifetime of
Badari Pulavarty wrote:
On Sat, 2007-06-30 at 10:13 -0400, Mingming Cao wrote:
On Fri, 2007-06-29 at 13:01 -0700, Andrew Morton wrote:
Guys, Mike and Sreenivasa at google are looking into implementing
fallocate() on ext2. Of course, any such implementation could and should
also be portable to
On Fri, 2007-07-06 at 14:33 -0700, Mike Waychison wrote:
Badari Pulavarty wrote:
On Sat, 2007-06-30 at 10:13 -0400, Mingming Cao wrote:
On Fri, 2007-06-29 at 13:01 -0700, Andrew Morton wrote:
Guys, Mike and Sreenivasa at google are looking into implementing
fallocate() on ext2. Of
On Fri, Jun 29, 2007 at 06:07:25PM -0400, Mike Waychison wrote:
Relying on (a tweaked) reservations code is also somewhat limitting at
this stage given that reservations are lost on close(fd). Unless we
change the lifetime of the reservations (maybe for the lifetime of the
in-core
On Sat, 2007-06-30 at 10:13 -0400, Mingming Cao wrote:
On Fri, 2007-06-29 at 13:01 -0700, Andrew Morton wrote:
Guys, Mike and Sreenivasa at google are looking into implementing
fallocate() on ext2. Of course, any such implementation could and should
also be portable to ext3 and ext4
On Sat, 2007-06-30 at 13:29 -0400, Andreas Dilger wrote:
On Jun 30, 2007 10:13 -0400, Mingming Cao wrote:
Another approach we have been thinking is using a backing
inode(per-inode-with-preallocation) to store the preallocated blocks.
When user asked for preallocation on the base inode,
On Fri, 2007-06-29 at 13:01 -0700, Andrew Morton wrote:
Guys, Mike and Sreenivasa at google are looking into implementing
fallocate() on ext2. Of course, any such implementation could and should
also be portable to ext3 and ext4 bitmapped files.
I believe that Sreenivasa will mainly be
On Sat, 2007-06-30 at 01:14 -0400, Andreas Dilger wrote:
On Jun 29, 2007 18:26 -0400, Mike Waychison wrote:
Andreas Dilger wrote:
I don't think ext2 is safe for 8TB filesystems anyways, so this
isn't a huge loss.
This is reference to the idea of overloading the high-bit and not
Guys, Mike and Sreenivasa at google are looking into implementing
fallocate() on ext2. Of course, any such implementation could and should
also be portable to ext3 and ext4 bitmapped files.
I believe that Sreenivasa will mainly be doing the implementation work.
The basic plan is as follows:
On Fri, 2007-06-29 at 13:01 -0700, Andrew Morton wrote:
Guys, Mike and Sreenivasa at google are looking into implementing
fallocate() on ext2. Of course, any such implementation could and should
also be portable to ext3 and ext4 bitmapped files.
I believe that Sreenivasa will mainly be
Dave Kleikamp wrote:
On Fri, 2007-06-29 at 13:01 -0700, Andrew Morton wrote:
Guys, Mike and Sreenivasa at google are looking into implementing
fallocate() on ext2. Of course, any such implementation could and should
also be portable to ext3 and ext4 bitmapped files.
I believe that Sreenivasa
On Fri, Jun 29, 2007 at 01:01:20PM -0700, Andrew Morton wrote:
Guys, Mike and Sreenivasa at google are looking into implementing
fallocate() on ext2. Of course, any such implementation could and should
also be portable to ext3 and ext4 bitmapped files.
What's the eventual goal of this work?
On Fri, 2007-06-29 at 16:52 -0400, Mike Waychison wrote:
Dave Kleikamp wrote:
By truncating the blocks file at the correct byte offset, only needing
to zero some bits of the last byte of the file.
We were thinking the unwritten blocks file would be indexed by physical
block number of
On Fri, 29 Jun 2007 16:55:25 -0400
Theodore Tso [EMAIL PROTECTED] wrote:
On Fri, Jun 29, 2007 at 01:01:20PM -0700, Andrew Morton wrote:
Guys, Mike and Sreenivasa at google are looking into implementing
fallocate() on ext2. Of course, any such implementation could and should
also be
On Jun 29, 2007 16:55 -0400, Theodore Tso wrote:
What's the eventual goal of this work? Would it be for mainline use,
or just something that would be used internally at Google? I'm not
particularly ennthused about supporting two ways of doing fallocate();
one for ext4 and one for
Andrew Morton wrote:
On Fri, 29 Jun 2007 16:55:25 -0400
Theodore Tso [EMAIL PROTECTED] wrote:
On Fri, Jun 29, 2007 at 01:01:20PM -0700, Andrew Morton wrote:
Guys, Mike and Sreenivasa at google are looking into implementing
fallocate() on ext2. Of course, any such implementation could and
Andreas Dilger wrote:
On Jun 29, 2007 16:55 -0400, Theodore Tso wrote:
What's the eventual goal of this work? Would it be for mainline use,
or just something that would be used internally at Google? I'm not
particularly ennthused about supporting two ways of doing fallocate();
one for ext4
On Jun 29, 2007 18:26 -0400, Mike Waychison wrote:
Andreas Dilger wrote:
I don't think ext2 is safe for 8TB filesystems anyways, so this
isn't a huge loss.
This is reference to the idea of overloading the high-bit and not
related to the PAGE_SIZE blocks correct?
Correct - just that the
18 matches
Mail list logo
