1. 05 10月, 2007 1 次提交
  2. 04 10月, 2007 1 次提交
  3. 03 10月, 2007 6 次提交
  4. 13 9月, 2007 1 次提交
  5. 24 7月, 2007 1 次提交
  6. 23 7月, 2007 1 次提交
  7. 20 7月, 2007 1 次提交
  8. 18 7月, 2007 1 次提交
  9. 17 7月, 2007 1 次提交
  10. 12 7月, 2007 1 次提交
  11. 29 6月, 2007 2 次提交
  12. 25 6月, 2007 1 次提交
  13. 14 6月, 2007 2 次提交
  14. 23 5月, 2007 1 次提交
  15. 12 5月, 2007 2 次提交
  16. 09 5月, 2007 3 次提交
    • H
      [POWERPC] Don't use SLAB/SLUB for PTE pages · 517e2263
      Hugh Dickins 提交于
      The SLUB allocator relies on struct page fields first_page and slab,
      overwritten by ptl when SPLIT_PTLOCK: so the SLUB allocator cannot then
      be used for the lowest level of pagetable pages.  This was obstructing
      SLUB on PowerPC, which uses kmem_caches for its pagetables.  So convert
      its pte level to use normal gfp pages (whereas pmd, pud and 64k-page pgd
      want partpages, so continue to use kmem_caches for pmd, pud and pgd).
      Signed-off-by: NHugh Dickins <hugh@veritas.com>
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      517e2263
    • B
      [POWERPC] Add ability to 4K kernel to hash in 64K pages · 16c2d476
      Benjamin Herrenschmidt 提交于
      This adds the ability for a kernel compiled with 4K page size
      to have special slices containing 64K pages and hash the right type
      of hash PTEs.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      16c2d476
    • B
      [POWERPC] Introduce address space "slices" · d0f13e3c
      Benjamin Herrenschmidt 提交于
      The basic issue is to be able to do what hugetlbfs does but with
      different page sizes for some other special filesystems; more
      specifically, my need is:
      
       - Huge pages
      
       - SPE local store mappings using 64K pages on a 4K base page size
      kernel on Cell
      
       - Some special 4K segments in 64K-page kernels for mapping a dodgy
      type of powerpc-specific infiniband hardware that requires 4K MMU
      mappings for various reasons I won't explain here.
      
      The main issues are:
      
       - To maintain/keep track of the page size per "segment" (as we can
      only have one page size per segment on powerpc, which are 256MB
      divisions of the address space).
      
       - To make sure special mappings stay within their allotted
      "segments" (including MAP_FIXED crap)
      
       - To make sure everybody else doesn't mmap/brk/grow_stack into a
      "segment" that is used for a special mapping
      
      Some of the necessary mechanisms to handle that were present in the
      hugetlbfs code, but mostly in ways not suitable for anything else.
      
      The patch relies on some changes to the generic get_unmapped_area()
      that just got merged.  It still hijacks hugetlb callbacks here or
      there as the generic code hasn't been entirely cleaned up yet but
      that shouldn't be a problem.
      
      So what is a slice ?  Well, I re-used the mechanism used formerly by our
      hugetlbfs implementation which divides the address space in
      "meta-segments" which I called "slices".  The division is done using
      256MB slices below 4G, and 1T slices above.  Thus the address space is
      divided currently into 16 "low" slices and 16 "high" slices.  (Special
      case: high slice 0 is the area between 4G and 1T).
      
      Doing so simplifies significantly the tracking of segments and avoids
      having to keep track of all the 256MB segments in the address space.
      
      While I used the "concepts" of hugetlbfs, I mostly re-implemented
      everything in a more generic way and "ported" hugetlbfs to it.
      
      Slices can have an associated page size, which is encoded in the mmu
      context and used by the SLB miss handler to set the segment sizes.  The
      hash code currently doesn't care, it has a specific check for hugepages,
      though I might add a mechanism to provide per-slice hash mapping
      functions in the future.
      
      The slice code provide a pair of "generic" get_unmapped_area() (bottomup
      and topdown) functions that should work with any slice size.  There is
      some trickiness here so I would appreciate people to have a look at the
      implementation of these and let me know if I got something wrong.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      d0f13e3c
  17. 08 5月, 2007 4 次提交
  18. 07 5月, 2007 1 次提交
  19. 02 5月, 2007 1 次提交
  20. 27 4月, 2007 1 次提交
  21. 24 4月, 2007 1 次提交
  22. 13 4月, 2007 6 次提交