[Nfd-dev] [Ndn-interest] content_store

[Giuseppe Carella]

*The default "priority fifo" CS replacement policy evicts stale Data (those
stayed longer than FreshnessPeriod) first, before evicting non-stale Data.*
*The overall capacity of the CS can be adjusted in nfd.conf at
tables.cs_max_packets attribute.*
    Where can I check and change the default replacement policy?

*This is a limitation of ndndump. Use NDN dissector for Wireshark
<https://github.com/named-data/ndn-tools/tree/master/tools/dissect-wireshark>
instead.*
    Does it mean all the packets arrive on the consumer side in a complete
way, even if it defines them as incomplete?

Thank you.

2017-12-26 15:28 GMT+01:00 Junxiao Shi <shijunxiao at email.arizona.edu>:

> Can you resend the reply to nfd-dev mailing list?
>
> On Dec 26, 2017 08:58, "Giuseppe Carella" <gcarella228 at gmail.com> wrote:
>
>> *The default "priority fifo" CS replacement policy evicts stale Data
>> (those stayed longer than FreshnessPeriod) first, before evicting non-stale
>> Data.*
>> *The overall capacity of the CS can be adjusted in nfd.conf at
>> tables.cs_max_packets attribute.*
>>     Where can I check and change the default replacement policy?
>>
>> *This is a limitation of ndndump. Use NDN dissector for Wireshark
>> <https://github.com/named-data/ndn-tools/tree/master/tools/dissect-wireshark>
>> instead.*
>>     Does it mean all the packets arrive on the consumer side in a
>> complete way, even if it defines them as incomplete?
>>
>> Thank you.
>> Giuseppe.
>>
>> 2017-12-26 14:41 GMT+01:00 Junxiao Shi <shijunxiao at email.arizona.edu>:
>>
>>> Hi Guiseppe
>>>
>>> Does it mean that the data is deleted from the CS after the
>>>> FreshnessPeriod is over?
>>>>
>>>
>>> No. Data that has stayed longer than FreshnessPeriod cannot satisfy
>>> Interest with MustBeFresh selector, but can still satisfy Interest without
>>> MustBeFresh selector.
>>> It is unnecessary to delete them.
>>>
>>>
>>>> It seems that I store so many data packets on the content store that
>>>> NFD is not able to work in a good way anymore.
>>>>
>>>
>>> The default "priority fifo" CS replacement policy evicts stale Data
>>> (those stayed longer than FreshnessPeriod) first, before evicting non-stale
>>> Data.
>>> The overall capacity of the CS can be adjusted in nfd.conf at
>>> tables.cs_max_packets attribute.
>>>
>>>
>>>> I get some data packets which are incomplete: sniffing the packet I
>>>> have "INCOMPLETE-PACKET".
>>>>
>>>
>>> This is a limitation of ndndump. Use NDN dissector for Wireshark
>>> <https://github.com/named-data/ndn-tools/tree/master/tools/dissect-wireshark>
>>> instead.
>>>
>>>
>>>> I think it is caused by the CS which is in overflow.
>>>>
>>>
>>> No. CS has a replacement policy and can never overflow.
>>>
>>>
>>>> There are some policies to manage the CS, but I think that the replace
>>>> policy is done automatically by NFD.
>>>>
>>>
>>>
>>> Yours, Junxiao
>>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20171226/3ddcd14e/attachment-0001.html>