libnl: initial cache fill

libnl: initial cache fill

[Volker Poplawski]

Hi all.

Why is
nl_cache_request_full_dump ()
not part of the public api of libnl?

Or do i miss the intended way for an initial cache fill when using the cache-
manager? 

And BTW: What actually is part of the public api?
The doxygen docs on libnl give no clue about what is for applications and what 
is used internally.



Greetings
....Volker

Re: libnl: initial cache fill

[Patrick McHardy]

Volker Poplawski wrote:
> Why is
> nl_cache_request_full_dump ()
> not part of the public api of libnl?
> 
> Or do i miss the intended way for an initial cache fill when using the cache-
> manager? 

I think you should use nl_cache_mngr_add(), which will dump the
current contents from the kernel and keep the cache up to date
using event messages. IIRC nl_cache_resync() is intended to be
used after receiving an ENOBUFS from the kernel (indicating that
an event message was lost) to trigger a resync. This is an expensive
operation however and may lead to event loss itself, so it probably
makes sense to slightly delay it after receiving an ENOBUFS to make
sure you don't make things worse.

> And BTW: What actually is part of the public api?
> The doxygen docs on libnl give no clue about what is for applications and what 
> is used internally.

Everything declared in one of the headers under include/netlink/
can be considered part of the public API.