[ECOS] What portions of eCos code can be locked in instruction cache

["sandeep" <sandeep at codito dot com>]

hi list,

in case you happen to get eCos working on a chip that has support for
instruction cache locking, what portions of eCos kernel would you suggest should
be locked there for optimal performance?

* HAL code that gets called often viz. context switch code, interrupt/exception
handling code
* roughly what section of network code?
* what part of kernel code? apart from scheduler related code, unlock_inner
function, isrs/dsrs

to instruction-cache-lock certain non-HAL code some changes may have to be made
to non-HAL code in eCos, eg. may be marking some functions with special
attributes. to what extents it is fine to modify the non-HAL eCos code? surely
coz of this syncing with global eCos CVS is going to be bit of hassles than
otherwise.

hoping to get your views.

peace
sandeep



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss