diff options
| author | H. Peter Anvin <hpa@zytor.com> | 2001-10-22 03:42:09 +0000 |
|---|---|---|
| committer | H. Peter Anvin <hpa@zytor.com> | 2001-10-22 03:42:09 +0000 |
| commit | b2e8ee2f623c3709fac717507f6b5aba51d8d355 (patch) | |
| tree | 19f4c640bb8a44df0c2f71389e8b11b550d42217 /README | |
| parent | 1abaff844c2ff1651f493822c28836e418137b2a (diff) | |
| download | lpsm-b2e8ee2f623c3709fac717507f6b5aba51d8d355.tar.gz lpsm-b2e8ee2f623c3709fac717507f6b5aba51d8d355.tar.xz lpsm-b2e8ee2f623c3709fac717507f6b5aba51d8d355.zip | |
Explain portability constraints.
Diffstat (limited to 'README')
| -rw-r--r-- | README | 9 |
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 due time. +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: |