On 16/09/14 13:42, Daniel Hellstrom wrote:
Hello,
what is the use case for the following functions:
rtems_cache_flush_multiple_data_lines_processor_set()
rtems_cache_invalidate_multiple_data_lines_processor_set()
rtems_cache_flush_entire_data_processor_set()
rtems_cache_invalidate_entire_data_processor_set()
?
Makes it sense on an SMP system running an operating system and application
in one address space to do processor specific cache operations?
The functions are currently unused (except for the test program).
I think most likely we want to flush/invalidate all CPUs in the system or only
the local CPU's cache. Why do you ask, have you found a reason to limit/change
the API?
For all CPUs, you have the standard functions.
The usage of "local CPU" is extremely dangerous since this makes only sense if
you are absolutely sure that you stay on the current processor long enough.
I am in favour of removing these new API calls in case there is no strong use
case.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
