linux.git/fs/ext2/dir.c, branch v4.5

pagemap.h: move dir_pages() over there

2015-06-23T22:02:00+00:00

That function was declared in a lot of filesystems to calculate
directory pages.

Signed-off-by: Fabian Frederick 
Signed-off-by: Al Viro

VFS: normal filesystems (and lustre): d_inode() annotations

2015-04-15T19:06:57+00:00

that's the bulk of filesystem drivers dealing with inodes of their own

Signed-off-by: David Howells 
Signed-off-by: Al Viro

[readdir] simple local unixlike: switch to ->iterate()

2013-06-29T08:46:47+00:00

ext2, ufs, minix, sysv

Signed-off-by: Al Viro

new helper: file_inode(file)

2013-02-23T04:31:31+00:00

Signed-off-by: Al Viro

ext2: remove the second argument of k[un]map_atomic()

2012-03-20T13:48:22+00:00

Acked-by: Jan Kara 
Signed-off-by: Cong Wang

ext2: propagate umode_t

2012-01-04T03:54:58+00:00

Signed-off-by: Al Viro

ext2: speed up file creates by optimizing rec_len functions

2011-01-10T18:04:06+00:00

The addition of 64k block capability in the rec_len_from_disk
and rec_len_to_disk functions added a bit of math overhead which
slows down file create workloads needlessly when the architecture
cannot even support 64k blocks, thanks to page size limits.

The directory entry checking can also be optimized a bit
by sprinkling in some unlikely() conditions to move the
error handling out of line.

bonnie++ sequential file creates on a 512MB ramdisk speeds up
from about 2200/s to about 2500/s, about a 14% improvement.

Signed-off-by: Eric Sandeen 
Signed-off-by: Jan Kara

fs: add sync_inode_metadata

2010-10-26T01:18:19+00:00

Add a new helper to write out the inode using the writeback code,
that is including the correct dirty bit and list manipulation.  A few
of filesystems already opencode this, and a lot of others should be
using it instead of using write_inode_now which also writes out the
data.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

introduce __block_write_begin

2010-08-09T20:47:32+00:00

Split up the block_write_begin implementation - __block_write_begin is a new
trivial wrapper for block_prepare_write that always takes an already
allocated page and can be either called from block_write_begin or filesystem
code that already has a page allocated.  Remove the handling of already
allocated pages from block_write_begin after switching all callers that
do it to __block_write_begin.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

clean up write_begin usage for directories in pagecache

2010-08-09T20:47:31+00:00

For filesystem that implement directories in pagecache we call
block_write_begin with an already allocated page for this code, while the
normal regular file write path uses the default block_write_begin behaviour.

Get rid of the __foofs_write_begin helper and opencode the normal write_begin
call in foofs_write_begin, while adding a new foofs_prepare_chunk helper for
the directory code.  The added benefit is that foofs_prepare_chunk has
a much saner calling convention.

Note that the interruptible flag passed into block_write_begin is always
ignored if we already pass in a page (see next patch for details), and
we never were doing truncations of exessive blocks for this case either so we
can switch directly to block_write_begin_newtrunc.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro