Lines Matching +full:address +full:- +full:aligned

23 from an address that is not evenly divisible by N (i.e. addr % N != 0).
24 For example, reading 4 bytes of data from address 0x10004 is fine, but
25 reading 4 bytes of data from address 0x10005 would be an unaligned memory
32 which will compile to multiple-byte memory access instructions, namely when
40 When accessing N bytes of memory, the base memory address must be evenly
59  - Some architectures are able to perform unaligned memory accesses
61  - Some architectures raise processor exceptions when unaligned accesses
64  - Some architectures raise processor exceptions when unaligned accesses
67  - Some architectures are not capable of unaligned memory access, but will
94 starting at address 0x10000. With a basic level of understanding, it would
97 structure, i.e. address 0x10002, but that address is not evenly divisible
103 to pad structures so that accesses to fields are suitably aligned (assuming
107 parameters to a naturally aligned scheme, based on the size of the type of
131 structure type. This GCC-specific attribute tells the compiler never to
141 non-packed case, so the packed attribute should only be used when avoiding
170 2 bytes (16 bits) to be read from memory starting at address addr1.
172 Think about what would happen if addr1 was an odd address such as 0x10003.
177 16-bit-aligned addresses. It is up to the caller to ensure this alignment or
178 not use this function at all. This alignment-unsafe function is still useful
193 to an address that is not evenly divisible by 4.
235 aligned memory, using these macros to access unaligned memory can be costly in
240 Due to the byte-wise nature of this operation, unaligned accesses are avoided.
246 On architectures that require aligned loads, networking requires that the IP
247 header is aligned on a four-byte boundary to optimise the IP stack. For
251 DMA to an address which can be expressed as 4*n + 2. One notable exception
256 4*n+2 or non-ethernet hardware, this can be a problem, and it is then
257 required to copy the incoming frame into an aligned buffer. Because this is