|author||H. Peter Anvin <firstname.lastname@example.org>||2001-10-22 03:42:09 +0000|
|committer||H. Peter Anvin <email@example.com>||2001-10-22 03:42:09 +0000|
Explain portability constraints.
Diffstat (limited to 'README')
1 files changed, 9 insertions, 0 deletions
@@ -15,10 +15,19 @@ IMPORTANT: I cannot at this stage guarantee that future versions of
the LPSM will be binary compatible. These are test releases. Use at
your own risk.
+LPSM DATABASES ARE NOT PORTABLE. This is pretty much inherent in the
+fact that the LPSM library does not attach any meaning to the data it
+stores. Therefore it is imperative that your application allows a way
+to dump its database contents in a portable form.
Currently the persistent memory database is not sharable nor
thread-safe. I'm hoping to resolve at least the latter condition in
+Because the persistent memory is mapped into memory at a fixed address
+(which varies with architecture) it is not possible to have more than
+one LPSM database mapped at any one time.
** Functionality description: