Dominic, > I think it would be better to provide cache manipulation calls defined > top-down (by their purpose); but so long as we are stuck with calls > which are defined as performing particular low-level actions, it's > surely dangerous to guess that we know what they are used for so we > can trim the functions accordingly... The API is not cast in stone -- if there's a justifiable benefit, appropriate fuctions can be added; either completely new ones (possibly inlined) or as an extension to cacheflush() (which still has 30 bits freely available). Maciej -- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available +
