[ndnSIM] Evicting a specific item from the content store (nfd::cs::Cs)

Igor Carvalho igfuca at gmail.com
Sat Nov 19 03:06:05 PST 2016

Hi, John.
About your last queation, I believe that this has not been implemented
because Cs  removals are performed by the replacement  policies (Lru/Fifo),
which makes it unnecessary the implementation of a specific piece of
content. If you go through  both implementations, they have the method that
is in charge this.


LruPolicy::doAfterInsert(iterator i)


  this->insertToQueue(i, true);



Hope that helps.


Em 19 de nov de 2016 05:05, "John Baugh" <jpbaugh at umich.edu> escreveu:

> Hello all:
> Okay, please correct me if I'm wrong:
> If I understand this correctly, when you create a custom Policy
> subclass/derived class, *the developer *is responsible for creating the
> three queues specified in the NFD Developer guide?  (unsolicited, stale,
> and fifo)?  So we directly control what stays in the "queues" (std::list)
> according the the policy that we can determine.  So the *Policy *maintains
> the actual Entries, while the Cs maintains the Table of names?  I noticed
> the three queues don't actually live in the cs.cpp or cs.hpp files.
> I'm *still * a little confused about the Cs::erase method:  why isn't it
> implemented?  How do we "trigger" a removal of an item from the Content
> Store (Policy?)
> Thanks,
> John
> On Fri, Nov 18, 2016 at 12:10 PM, John Baugh <jpbaugh at umich.edu> wrote:
>> Sorry to be bothersome - I've continued working on this and haven't made
>> a solution yet.  Any ideas?
>> Thanks,
>> John
>> On Fri, Nov 18, 2016 at 3:56 AM, John Baugh <jpbaugh at umich.edu> wrote:
>>> Greetings all,
>>> 1.)  When I tried to use the erase( ) function to remove an item, I
>>> found out that the method is not implemented.  I checked the code from the
>>> documentation and found out that this is indeed the case.
>>> So how am I supposed to evict a specific item from the Content Store?
>>> 2.)  I've noticed when I use ./waf --run=some-test that the system often
>>> re-compiles tons of completely (as far as I know) unrelated files (the grid
>>> samples, tracers, etc.).  This adds significantly to the time it takes to
>>> run the test.  Any ideas why this might be happening?  I'm not using any of
>>> the sample files, tracers, etc. - nor have I modified them for my current
>>> tests.
>>> Thanks,
>>> John
> _______________________________________________
> ndnSIM mailing list
> ndnSIM at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20161119/132f6ce7/attachment.html>

More information about the ndnSIM mailing list