Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history
yaml
---
r: 77808
b: refs/heads/master
c: 66d485b
h: refs/heads/master
v: v3
  • Loading branch information
Paul Mundt committed Jan 28, 2008
1 parent 51ec188 commit b5356aa
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 14 deletions.
2 changes: 1 addition & 1 deletion [refs]
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
---
refs/heads/master: eddeeb32fe303910c58c4e3c27fde4b6f1503350
refs/heads/master: 66d485b45a5493f6a2ca067c6f472e7b2ca342c2
22 changes: 9 additions & 13 deletions trunk/include/asm-sh/page.h
Original file line number Diff line number Diff line change
Expand Up @@ -138,22 +138,18 @@ typedef struct { unsigned long pgd; } pgd_t;
#endif

/*
* Slub defaults to 8-byte alignment, we're only interested in 4.
* Slab defaults to BYTES_PER_WORD, which ends up being the same anyways.
* Some drivers need to perform DMA into kmalloc'ed buffers
* and so we have to increase the kmalloc minalign for this.
*/
#ifdef CONFIG_SUPERH32
#define ARCH_KMALLOC_MINALIGN 4
#define ARCH_SLAB_MINALIGN 4
#else
/* If gcc inlines memset, it will use st.q instructions. Therefore, we need
kmalloc allocations to be 8-byte aligned. Without this, the alignment
becomes BYTE_PER_WORD i.e. only 4 (since sizeof(long)==sizeof(void*)==4 on
sh64 at the moment). */
#define ARCH_KMALLOC_MINALIGN 8
#define ARCH_KMALLOC_MINALIGN L1_CACHE_BYTES

#ifdef CONFIG_SUPERH64
/*
* We want 8-byte alignment for the slab caches as well, otherwise we have
* the same BYTES_PER_WORD (sizeof(void *)) min align in kmem_cache_create().
* While BYTES_PER_WORD == 4 on the current sh64 ABI, GCC will still
* happily generate {ld/st}.q pairs, requiring us to have 8-byte
* alignment to avoid traps. The kmalloc alignment is gauranteed by
* virtue of L1_CACHE_BYTES, requiring this to only be special cased
* for slab caches.
*/
#define ARCH_SLAB_MINALIGN 8
#endif
Expand Down

0 comments on commit b5356aa

Please sign in to comment.