[ndnSIM] Creating a custom cache-replacement policy in CS?

shijunxiao at email.arizona.edu shijunxiao at email.arizona.edu
Sun Oct 23 11:09:49 PDT 2016


Hi John

ndnSIM 2.1 uses a fork of NFD 0.3.4 release, which contains a ContentStore policy API, and it is somewhat flexible. NFD 0.3.4 offers a priority-fifo policy and a LRU policy, implemented with this policy API. See NFD developer guide for more information.

I saw the incorrect statement on http://ndnsim.net/2.1/cs.html . I have reported ndnSIM Bug 3827, so that ndnSIM developers can correct that statement in the next release.

Yours, Junxiao

From: John Baugh
Sent: Sunday, October 23, 2016 10:56
To: Junxiao Shi
Subject: Re: [ndnSIM] Creating a custom cache-replacement policy in CS?

The documentation and tutorials say that NFD has a hard coded cache replacement policy and is not flexible.  Then it describes that this is why the ndnSIM 1.0 CS has been ported into 2.0.

On Oct 23, 2016 11:16 AM, "Junxiao Shi" <shijunxiao at email.arizona.edu> wrote:
Hi John

Can you elaborate on this statement? Exactly what is missing in NFD 0.3.4's ContentStore policy API that is present in ndnSIM 1.0 ContentStore API?
Your answer to this can allow NFD designers to either point out your misunderstand and help you use NFD ContentStore policy API to achieve what you need to do, or improve future versions of NFD so that it becomes more flexible with cache replacement policies.

Yours, Junxiao

On Sat, Oct 22, 2016 at 7:51 PM, John Baugh <jpbaugh at umich.edu> wrote:

Since the NFD Content Store appears to not be flexible with cache replacement policies, I am going to steer away from it.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20161023/125e7d0f/attachment.html>


More information about the ndnSIM mailing list