| commit | 3d1074349b22c9653e746282564136c87668c2b8 | |
| author | Russell King <rmk+kernel@arm.linux.org.uk> | |
| Thu, 19 Nov 2009 11:41:09 +0000 (19 11:41 +0000) | ||
| committer | Russell King <rmk+kernel@arm.linux.org.uk> | |
| Mon, 14 Dec 2009 13:35:13 +0000 (14 13:35 +0000) | ||
| tree | b86a8b3cfa5b63e218df8da66417a4ec5f229b0e | treesnapshot (tar.gz zip) |
| parent | 0eb948dd7f7c3cec37440c16a6c738c8e75efcda | commitdiff |
ARM: cache-l2x0: make better use of background cache handling
There's no point having the hardware support background operations
if we issue a cache operation, and then wait for it to complete
before calculating the address of the next operation. We gain no
advantage in the cache controller stalling the bus until completion.
What we should be doing is using the 'wait' time productively by
calculating the address of the next operation, and only then waiting
for the previous operation to complete. This means that cache
operations can occur in parallel with the CPU calculating the next
address.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
There's no point having the hardware support background operations
if we issue a cache operation, and then wait for it to complete
before calculating the address of the next operation. We gain no
advantage in the cache controller stalling the bus until completion.
What we should be doing is using the 'wait' time productively by
calculating the address of the next operation, and only then waiting
for the previous operation to complete. This means that cache
operations can occur in parallel with the CPU calculating the next
address.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
| arch/arm/mm/cache-l2x0.c | diffblobblamehistory |