14.4.1 Double Linefill Issuing

The L2CC cache line length is 32-byte. Therefore, by default, on each L2 cache miss, the L2CC issues 32-byte linefills, 4 x 64-bit read bursts, to the L3 memory system. The L2CC can issue 64-byte linefills, 8 x 64-bit read bursts, on an L2 cache miss. When the L2CC is waiting for the data from L3, it performs a lookup on the second cache line targeted by the 64-byte linefill. If it misses, data corresponding to the second cache line are allocated to the L2 cache. If it hits, data corresponding to the second cache line are discarded.

The user can control this feature using the DLEN, DLFWRDIS and DLEN bits of the L2CC Prefetch Control Register. The IDLEN and DLFWRDIS bits are only used if the user sets the DLEN bit HIGH. The table below shows the behavior of the L2CC host ports, depending on the configuration chosen by the user.

Table 14-1. L2CC Host Port Behavior
Bit 30

DLEN

Bit 27

DLFWRDIS

Bit 23

IDLEN

Original Read Address from L1Read Address to L3CPU System Bus Burst TypeCPU System Bus Burst LengthTargeted Cache Lines
00 or 10 or 10x000x00WRAP0x3, 4x64-bit0x00
00 or 10 or 10x200x20WRAP0x3, 4x64-bit0x20
10 or 100x000x00WRAP0x7, 8x64-bit0x00 and 0x20
1100x08 or 0x10 or 0x180x08WRAP0x3, 4x64-bit0x00
1000x08 or 0x10 or 0x180x00WRAP0x7, 8x64-bit0x00 and 0x20
10 or 100x200x20WRAP0x7, 8x64-bit0x00 and 0x20
1100x28 or 0x30 or 0x380x28WRAP0x3, 4x64-bit0x20
1000x28 or 0x30 or 0x380x20WRAP0x7, 8x64-bit0x00 and 0x20
10 or 110x000x00INCR or WRAP0x7, 8x64-bit0x00 and 0x20
1110x08 or 0x10 or 0x180x08WRAP0x3, 4x64-bit0x00
1010x08 or 0x10 or 0x180x00INCR or WRAP0x7, 8x64-bit0x00 and 0x20
10 or 110x200x20INCR0x7, 8x64-bit0x20 and 0x40
1110x28 or 0x30 or 0x380x28WRAP0x3, 4x64-bit0x20
1010x28 or 0x30 or 0x380x20INCR0x7, 8x64-bit0x20 and 0x40
Note:
  1. Double linefills are not issued for prefetch reads if exclusive cache configuration is enabled.
  2. Double linefills are not launched when crossing a 4-Kbyte boundary.
  3. Double linefills only occur if a WRAP4 or an INCR4 64-bit transaction is received on the client ports. This transaction is most commonly seen as a result of a cache linefill in a host, but can be produced by a host when accessing memory marked as inner non-cacheable.