cacheflush
(2)flush contents of instruction and/or data cache
LIBRARY
DESCRIPTION
RETURN VALUE
ERRORS
VERSIONS
cacheflush() should not be used in programs intended to be portable. On Linux, this call first appeared on the MIPS architecture, but nowadays, Linux provides a cacheflush() system call on some other architectures, but with different arguments.
Architecture-specific variants
glibc provides a wrapper for this system call, with the prototype shown in SYNOPSIS, for the following architectures: ARC, CSKY, MIPS, and NIOS2.
On some other architectures, Linux provides this system call, with different arguments:
- M68K:
-
int cacheflush(unsigned long addr, int scope, int cache, unsigned long len); - SH:
-
int cacheflush(unsigned long addr, unsigned long len, int op);
- NDS32:
-
int cacheflush(unsigned int start, unsigned int end, int cache);
On the above architectures, glibc does not provide a wrapper for this system call; call it using syscall(2).
GCC alternative
Unless you need the finer grained control that this system call provides, you probably want to use the GCC built-in function __builtin___clear_cache(), which provides a portable interface across platforms supported by GCC and compatible compilers:
void __builtin___clear_cache(void *begin, void *end);
On platforms that don't require instruction cache flushes, __builtin___clear_cache() has no effect.
Note: On some GCC-compatible compilers, the prototype for this built-in function uses char * instead of void * for the parameters.