246
of size 64 at address 0x7F3220C55000 (offset 0x0 in /mnt/pmem/file)
in /data/listing_12-35!flush at listing_12-35.c:45 - 0x674
in /data/listing_12-35!main at listing_12-35.c:64 - 0x73F
in /lib64/libc.so.6!__libc_start_main at :
- 0x223D3
in /data/listing_12-35!_start at : - 0x574
is redundant with regard to
cache flush
of size 64 at address 0x7F3220C55000 (offset 0x0 in /mnt/pmem/file)
in /data/listing_12-35!flush at listing_12-35.c:45 - 0x674
in /data/listing_12-35!main at listing_12-35.c:65 - 0x750
in /lib64/libc.so.6!__libc_start_main at :
- 0x223D3
in /data/listing_12-35!_start at : - 0x574
of
memory store
of size 4 at address 0x7F3220C55000 (offset 0x0 in /mnt/pmem/file)
in /data/listing_12-35!main at listing_12-35.c:63 - 0x72D
in /lib64/libc.so.6!__libc_start_main at :
- 0x223D3
in /data/listing_12-35!_start at : - 0x574
The Persistence Inspector report warns about the redundant cache flush within
the main() function on line 65 of the listing_12-35.c program file – “main at
listing_12-35.c:65”. Solving these issues is as easy as deleting all the unnecessary
flushes, and the result will improve the application’s performance.
Chapter 12 Debugging persistent MeMory appliCations