What's peer manager default GC policy when buffer is full?

[Ben_nrf52840]

Hi,

Would you please explain the default behavior of peer manager Garbage collection when buffer is full if I don't call Garbage Collection?

I have tested with small number of phones until buffer full and seems GC removes duplicated phone information and keeps only one instance of phone information.

However, I don't understand when I make a buffer full with more than 60 phones which is enough to make a buffer full for 3 FDS_VIRTUAL_PAGES.

I noticed that sometimes the buffer is not cleared, but sometimes the buffer is cleared.

My question is as following.

- If there are small number of phone information is stored then GC keeps stored phone information with removing duplicated information. Is it correct?

- If there are no duplicated phone information stored then GC removes all phone information? or keeps all phone information w/o performing GC?

And Is there any detail document which explains garbage collection?

Regards,

Ben

[Sigurd]

Hi,

Documentation for the Peer Manager can be found here: https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.2/lib_peer_manager.html

Garbage collection reclaims the flash space that is occupied by records that have been deleted, or that failed to be completely written due to, for example, a power loss.

Usually, you will call pm_handler_flash_clean()  in pm_evt_handler(), https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_nrf5_v17.0.2%2Flib_pm_usage.html&cp=8_1_3_2_7_2_2&anchor=lib_pm_usage_events

and pm_handler_flash_clean() will do the following:

• Ranks peers by when they last connected.
• Garbage collects the flash when needed.
• Deletes the lowest ranked peer(s) when garbage collection is insufficient.

And Is there any detail document which explains garbage collection?

Yes, here: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_nrf5_v17.0.2%2Flib_fds_functionality.html&cp=8_1_3_16_1_2&anchor=lib_fds_functionality_gc