Bob and Steve,
On Tue, Nov 3, 2015 at 8:02 PM, Steven Whitehouse wrote:
>> Most of this looks good. However, two comments:
>>
>> 1. I don't like adding a new u16 to the gfs2_inode. I've been working to
>> reduce the size of gfs2's inodes lately, so I'd rather see this
>> implemented as a
Hi,
On 03/11/15 17:29, Bob Peterson wrote:
- Original Message -
When gfs2 allocates an inode and its extended attribute block next to
each other at inode create time, the inode's directory entry indicates
that in de_rahead. In that case, we can readahead the extended
attribute block wh
- Original Message -
> When gfs2 allocates an inode and its extended attribute block next to
> each other at inode create time, the inode's directory entry indicates
> that in de_rahead. In that case, we can readahead the extended
> attribute block when we read in the inode.
>
> Signed-of
When gfs2 allocates an inode and its extended attribute block next to
each other at inode create time, the inode's directory entry indicates
that in de_rahead. In that case, we can readahead the extended
attribute block when we read in the inode.
Signed-off-by: Andreas Gruenbacher
---
fs/gfs2/d
