Hi Lissiyas, Yes, the data packet is 72 bytes and can be configured in Ruby (See https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/src/mem/ruby/network/Network.cc#66 ) The address that you are seeing is the simulated virtual address that the message is carrying data for. This address will depend on the memory that your simulated system is supporting and the configuration in gem5.
The simulated message object in gem5 does not necessarily carry the same amount of data and address bits. It also has many other meta data information for analysis and debugging as you can see in the print of the message. Thanks, Srikant On Mon, Apr 3, 2023 at 3:37 AM Lissiyas Antony <jvlissi...@gmail.com> wrote: > Hello Srikant. > > Sorry for the delayed reply and thank you for your information. I've got > the data block values. > However, I am a little confused regarding the block size and address size. > > For example, for the below packet:- > > [PacketId=11144 Type=0 [ResponseMsg: addr = [0xd5e040, line 0xd5e040] Type > = MEMORY_DATA Sender = Directory-12 Destination = [NetDest (20) - 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 - 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - - 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 - - - - - - - - - - - - - - - - ] > DataBlk = [ 0x77 0x8 0xf 0xb6 0x44 0x24 0x1e 0x48 0xf7 0xd8 0x48 0x83 0xc4 > 0x28 0x5b 0x5d 0x41 0x5c 0x41 0x5d 0x41 0x5e 0x41 0x5f 0xc3 0x48 0xc7 0xc0 > 0xff 0xff 0xff 0xff 0xc3 0x66 0x66 0x2e 0xf 0x1f 0x84 0x0 0x0 0x0 0x0 0x0 > 0xf 0x1f 0x40 0x0 0x41 0x57 0x41 0x56 0x41 0x55 0x41 0x54 0x55 0x53 0x48 > 0x81 0xec 0xa0 0x0 0x0 ] Dirty = 0 AckCount = 0 MessageSize = Response_Data > ],Src Router=12 Dest Router=1 ] > > I believe by default GARNET, the data packets have a payload of 576 > bits/72 byte (64-bit address and 512-bit data). But the addr = 0xd5e040 > is 24 bits. > > Could you please let me know the default address size or what size the ' > addr = [0xd5e040,' referring to. > > Looking forward to hearing from you. > > Thanks. > Lissiyas Antony > > > > On Thu, 23 Mar 2023 at 22:49, Srikant Bharadwaj <srikan...@gmail.com> > wrote: > >> The DataBlk should show the correct hex values. However, you might be >> looking at data requests. Ensure that you look at data responses when >> loading data. >> What kind of application/workload are you running? Synthetic simulations >> always have 0x0 data values in packets. >> >> Srikant >> >> >> On Thu, Mar 23, 2023 at 3:21 AM Lissiyas Antony via gem5-users < >> gem5-users@gem5.org> wrote: >> >>> Hello there, >>> >>> Somebody help me with , to print the content of the Packets in hex >>> values. >>> >>> I've dereference a pointer '*m_msg_ptr* ' ,However DataBlk of all the >>> packets are showing 0x0; >>> >>> [RequestMsg: addr = [0x40, line 0x40] Type = MSG Requestor = L1Cache-0 >>> Destination = [NetDest (20) - 0 0 0 0 - - - 0 1 0 0 - - - - - - >>> - - - - - - - - - - ] DataBlk = [ 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 >>> 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 >>> 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 >>> 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 ] >>> MessageSize = Control ] >>> >>> Is there any other option to display the content in the network >>> interface before the *flitisizeMessage.* >>> >>> any comments would be appreciated. >>> >>> Regards, >>> Lissiyas Antony >>> >>> -- >>> LISSIYAS ANTONY >>> >>> _______________________________________________ >>> gem5-users mailing list -- gem5-users@gem5.org >>> To unsubscribe send an email to gem5-users-le...@gem5.org >>> >> > > -- > LISSIYAS ANTONY > >
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
