Known Issues

From liblfds.org
Revision as of 11:25, 18 February 2017 by Admin (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

liblfds

No known issues.

libshared

  • 31st May 2016 - The Linux kernel abstraction layer port is incomplete.

libtest

  • 18th Feburary 2017 - some test will spuriously fail if they do not complete at least one internal iteration of the data test; this has been observed on the ringbuffer write test, on ARM32, on a Raspberry Pi 2. Currently there is a performance issue with the unbounded/many/many queue on ARM32 (this was missed when 7.1.0 was released - too many bars on the bar graph!) and this in particular causes this problem on ARM32.

libbenchmark

  • 31st May 2016 - The Linux kernel abstraction layer port is incomplete.
  • 31st May 2016 - The btree test is a bit unfair - it does a bit more work as the number of logical cores increases, so as such, it is underplaying performance for higher core counts.

test

  • 31st May 2016 - If using shared object versions of liblfds libraries, cannot link on ARM32. Quite possibly not a liblfds bug, but still an issue.

benchmark

  • 31st May 2016 - If using shared object versions of liblfds libraries, cannot link on ARM32. Quite possibly not a liblfds bug, but still an issue.
  • 19th Aug 2016 - huge bug; builds using "gcc_gnumake_hosted_liblfds711_liblfds700" all crash, because some code involved in benchmark init effectively assumes NUMA. To work around this, install libnuma-devel (name varies a little by platform) and compile the "gcc_gnumake_hosted_liblfds711_liblfds700_libnuma" variant.

See Also