Re: [Gems-users] how get the message's source NodeID or source InterfaceID

["Zhang Yu" <thuzhangyu@xxxxxxxxx>]

Thanks. I think this is clear enough.

Yu

On Fri, May 9, 2008 at 5:30 PM, Niket <niketa@xxxxxxxxxxxxx> wrote:

Okay, I used to cout the messages and used to observe the requestors.
But the class Message or NetworkMessage do not have a field called
Requestor.

If you look into the files like RequestMsg.h, ResponseMsg.h, etc in the
generated protocol folder, you will see that they have private variables
RequestorID, SenderID, so on.

I think a way to get RequestorID/SenderID would be to look at the vnet
of the message and then infer which message type it is from.
You can typecast the Message to that type and get the
RequestorID/SenderID. This technique however would be tied to a
particular protocol.

A generic way of doing this would be to include the RequestorID,
SenderID, etc variables in Message.h and change the <protocol>-msg.sm
file to not declare these fields.

I am not sure how clear I am but I came up with this rightaway.

Cheers,
Niket

Zhang Yu wrote:
> Hi,
>
> I couldn't find the requestor  id function you mentioned. Can you tell
> me where it is?
>
> Thanks,
> Yu
>
> On Wed, Apr 9, 2008 at 10:49 AM, Niket <niketa@xxxxxxxxxxxxx

> <mailto:niketa@xxxxxxxxxxxxx>> wrote:
>
>     Each flit contains a message pointer which in turn has the
>     Requestor id.
>     You can convert this Requestor id to an interface id in a manner it is
>     done for the destination in the NI code.
>
>     Cheers,
>     Niket
>
>     ? wrote:
>     > In the Priceton network simulater
>     garnet-fixed-pipeline/NetworkInterface_d.c file,
>     > we see that:
>     >  when inNetLink->isReady() we pick a flit for this NI and
>     caculate the queue
>     > latency and network latency. I can easily get the message's
>     destination
>     > InterfaceID from the private data member m_id, but how can I get
>     the flit's source
>     > InterfaceID?
>     >
>     >
>     > _______________________________________________
>     > Gems-users mailing list

>     > Gems-users@xxxxxxxxxxx <mailto:Gems-users@xxxxxxxxxxx>

>     > https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>     > Use Google to search the GEMS Users mailing list by adding
>     "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
>     >
>     >
>
>     _______________________________________________
>     Gems-users mailing list

>     Gems-users@xxxxxxxxxxx <mailto:Gems-users@xxxxxxxxxxx>

>     https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>     Use Google to search the GEMS Users mailing list by adding
>     "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
>
>

_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.