[ofw] RE: [PATCH] NDProvider: Use private heap for memory allocations
Sean Hefty
sean.hefty at intel.com
Wed May 20 15:09:20 PDT 2009
>Which heap you use is up to you. The SecureMemoryCacheCallback requires that
The lower level libraries aren't calling SecureMemoryCacheCallback. The apps
(upper libraries) are. Why can't the apps use a different heap for this?
Look at it this way. The ND provider, winverbs, libibverbs, etc aren't doing
anything wrong, yet they're having to change because something breaks in higher
level code.
More information about the ofw
mailing list