Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
大约 1 年 前同步成功

通知 158
Star 36
Fork 7
cloud-kernel
cloud-kernel

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 10 2月, 2007 2 次提交
    • E
      [XFS] Remove unused header files for MAC and CAP checking functionality. · 7bc5306d
      由 Eric Sandeen 提交于 
      xfs_mac.h and xfs_cap.h provide definitions and macros that aren't used
anywhere in XFS at all. They are left-overs from "to be implement at some
point in the future" functionality that Irix XFS has. If this
functionality ever goes into Linux, it will be provided at a different
layer, most likely through the security hooks in the kernel so we will
never need this functionality in XFS.

Patch provided by Eric Sandeen (sandeen@sandeen.net).

SGI-PV: 960895
SGI-Modid: xfs-linux-melb:xfs-kern:28036a
Signed-off-by: NEric Sandeen <sandeen@sandeen.net>
Signed-off-by: NDavid Chinner <dgc@sgi.com>
Signed-off-by: NTim Shimmin <tes@sgi.com>
      7bc5306d
    • D
      [XFS] Keep stack usage down for 4k stacks by using noinline. · 7989cb8e
      由 David Chinner 提交于 
      gcc-4.1 and more recent aggressively inline static functions which
increases XFS stack usage by ~15% in critical paths. Prevent this from
occurring by adding noinline to the STATIC definition.

Also uninline some functions that are too large to be inlined and were
causing problems with CONFIG_FORCED_INLINING=y.

Finally, clean up all the different users of inline, __inline and
__inline__ and put them under one STATIC_INLINE macro. For debug kernels
the STATIC_INLINE macro uninlines those functions.

SGI-PV: 957159
SGI-Modid: xfs-linux-melb:xfs-kern:27585a
Signed-off-by: NDavid Chinner <dgc@sgi.com>
Signed-off-by: NDavid Chatterton <chatz@sgi.com>
Signed-off-by: NTim Shimmin <tes@sgi.com>
      7989cb8e
  3. 28 9月, 2006 3 次提交
  5. 20 6月, 2006 1 次提交
  7. 09 6月, 2006 2 次提交
  9. 31 3月, 2006 1 次提交
  11. 29 3月, 2006 1 次提交
  13. 14 3月, 2006 2 次提交
    • M
      [XFS] 929045 567344 This mod re-organizes some of the in-core file extent · 4eea22f0
      由 Mandy Kirkconnell 提交于 
      code to prepare for an upcoming mod which will introduce multi-level
in-core extent allocations. Although the in-core extent management is
using a new code path in this mod, the functionality remains the same. 
Major changes include:	- Introduce 10 new subroutines which re-orgainze
the existing code but	do NOT change functionality:	    
xfs_iext_get_ext()	   xfs_iext_insert()	     xfs_iext_add()	  
 xfs_iext_remove()	   xfs_iext_remove_inline()	   
xfs_iext_remove_direct()	 xfs_iext_realloc_direct()	  
xfs_iext_direct_to_inline()	    xfs_iext_inline_to_direct()        
xfs_iext_destroy() - Remove 2 subroutines (functionality moved to new
subroutines above):	    xfs_iext_realloc() -replaced by xfs_iext_add()
and xfs_iext_remove()	      xfs_bmap_insert_exlist() - replaced by
xfs_iext_insert()	  xfs_bmap_delete_exlist() - replaced by
xfs_iext_remove() - Replace all hard-coded (indexed) extent assignments
with a call to	 xfs_iext_get_ext() - Replace all extent record pointer
arithmetic (ep++, ep--, base + lastx,..)   with calls to
xfs_iext_get_ext() - Update comments to remove the idea of a single
"extent list" and   introduce "extent record" terminology instead

SGI-PV: 928864
SGI-Modid: xfs-linux-melb:xfs-kern:207390a
Signed-off-by: NMandy Kirkconnell <alkirkco@sgi.com>
Signed-off-by: NNathan Scott <nathans@sgi.com>
      4eea22f0
    • N
      [XFS] Fix a mutex_destroy diagnostic about a locked-mutex-on-destroy from · 20722a91
      由 Nathan Scott 提交于 
      quota code.

SGI-PV: 949149
SGI-Modid: xfs-linux-melb:xfs-kern:25123a
Signed-off-by: NNathan Scott <nathans@sgi.com>
      20722a91
  15. 28 2月, 2006 1 次提交
  17. 16 1月, 2006 1 次提交
  19. 15 1月, 2006 1 次提交
  21. 11 1月, 2006 2 次提交
  23. 10 1月, 2006 1 次提交
  25. 16 12月, 2005 1 次提交
  27. 02 11月, 2005 4 次提交
  29. 05 9月, 2005 1 次提交
  31. 02 9月, 2005 1 次提交
  33. 21 6月, 2005 4 次提交
  35. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      由 Linus Torvalds 提交于 
      Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!
      1da177e4