[ndnSIM] Cache hits/misses on producer node

Hassan Sinky sinkyh at oregonstate.edu
Thu Apr 14 10:24:16 PDT 2016


Perfect. That explains it. In that case then. How does the producer
differentiate if an interest has traversed a disjoint path with previous
interests?

Thanks!

On Thu, Apr 14, 2016 at 10:10 AM, Spyridon (Spyros) Mastorakis <
mastorakis at cs.ucla.edu> wrote:

> Hi,
>
> I am not sure I fully understand your question, but I will try to
> elaborate on it a little bit and you will let me know whether my response
> answers your question.
>
> A producer in ndnSIM is a node that has an application installed and
> running on it. To this end, it has a Contest Store like any other node. If
> the producer sends out some data packets, they will be in its CS in the
> near future. If some consumers request this data, but the Interest is
> forwarded to the producer through a path that is disjoint with the previous
> path, then the data will be served from the CS on the producer node.
>
> Does that answer your question?
>
> Thanks,
>
> Spyridon (Spyros) Mastorakis
> Personal Website: http://cs.ucla.edu/~mastorakis/
> Internet Research Laboratory
> Computer Science Department
> UCLA
>
> On Apr 14, 2016, at 2:33 AM, Hassan Sinky <sinkyh at oregonstate.edu> wrote:
>
> Hello everyone,
>
> I was just wondering what could be some cases when a producer node would
> register a cache hit? I assumed that if an interest request were to arrive
> at a producer it would simply process that request by returning the
> corresponding data. I have a topology with multiple producers of the same
> prefix and I installed the CS tracer only on the producers. I also have
> consumers requesting the prefix provided by the producers. The CS trace
> on the producers is registering cache hits and misses. Why would there be a
> hit or a miss? Should both simply be zero? Or am I missing something?
>
> Thanks!
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20160414/5d4eb3bf/attachment.html>


More information about the ndnSIM mailing list