Skip to content

K
kernel_linux

OpenHarmony / kernel_linux
上一次同步 3 年多

通知 13
Star 8
Fork 2
K
kernel_linux
切换分支/标签
  1. 19 5月, 2006 5 次提交
  3. 17 5月, 2006 1 次提交
  5. 13 5月, 2006 3 次提交
    • S
      [GFS2] Fix attributes setting logic · b9cb9813
      由 Steven Whitehouse 提交于 
      The attributes logic for immutable was wrong so that there was
not way to remove this attribute once set. This fixes the
bug.
Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      b9cb9813
    • S
      [GFS2] Remove incorrect initialisation of gh_owner · 9801f646
      由 Steven Whitehouse 提交于 
      The gh_owner field shouldn't be set or reset outside the glock code.
These were left over from when recursive locking was allowed. It
isn't any more, so they are not needed.
Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      9801f646
    • S
      [GFS2] Reverse block order in build_height · e90c01e1
      由 Steven Whitehouse 提交于 
      The original code ordered the blocks allocated in the build_height
routine backwards causing excessive disk seeks during a read of the
metadata. This patch reverses the order to try and reduce disk seeks.

Example: A five level metadata tree, I = Inode, P = Pointers, D = Data

You need to read the blocks in the order:

I P5 P4 P3 P2 P1 D

in order to read a single data block. The new code now orders the blocks
in this way. The old code used to order them as:

I P1 P2 P3 P4 P5 D

requiring two extra seeks on average. Note that for files which are
grown by gradual extension rather than by truncate or by llseek/write
at a large offset, this doesn't apply. In the case of writing to a
file linearly, this routine will only be called upon to extend the
height of the tree by one block at a time, so the ordering is
determined by when its called rather than by the internals of the
routine itself. Optimising that part of the ordering is a much
harder problem.
Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      e90c01e1
  7. 08 5月, 2006 4 次提交
  9. 06 5月, 2006 2 次提交
    • S
      [GFS2] Readpages support · fd88de56
      由 Steven Whitehouse 提交于 
      This adds readpages support (and also corrects a small bug in
the readpage error path at the same time). Hopefully this will
improve performance by allowing GFS to submit larger lumps of
I/O at a time.

In order to simplify the setting of BH_Boundary, it currently gets
set when we hit the end of a indirect pointer block. There is
always a boundary at this point with the current allocation code.
It doesn't get all the boundaries right though, so there is still
room for improvement in this.

See comments in fs/gfs2/ops_address.c for further information about
readpages with GFS2.

Signed-off-by: Steven Whitehouse
      fd88de56
    • R
      [GFS2] Set d_ops for root inode · 5bb76af1
      由 Robert S Peterson 提交于 
      Well, I managed to track down the bug in gfs2 that was causing
my grief.  Below is a patch for the problem.  Please incorporate
as you see fit.  Or should I say: as you see git.

The problem was basically that you never set d_ops for the root
inode, so the wrong hash algorithm was being used.  But only for
the root directory.  Turns out that if I used subdirectories, it
used the proper hash and my files were found just fine.
Signed-off-by: NRobert S Peterson <rpeterso@redhat.com>
Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      5bb76af1
  11. 04 5月, 2006 6 次提交
  13. 03 5月, 2006 2 次提交
  15. 02 5月, 2006 10 次提交
  17. 30 4月, 2006 1 次提交
  19. 28 4月, 2006 6 次提交