Lines Matching refs:packet

232         // queue the packet for deletion, as the sending cache is
358 // of the bus, if the packet comes from it.
363 // Here we reset the timing of the packet.
368 // the packet in a response
411 "%s saw a non-zero packet delay\n", name());
563 DPRINTF(CacheVerbose, "%s: packet %s found block: %s\n",
697 // memory address into the packet
785 // that we send the packet straight away, so do not
789 // free the request and packet
917 // the packet as a return value from this atomic op
984 // A tag-only access has to wait for the packet to arrive in order to
1047 // packet.
1049 // Calculate access latency on top of when the packet arrives. This
1059 // possible cases can be of a CleanEvict packet coming from above
1076 // packet is deleted in the crossbar. Hence, none of
1163 // if the packet does not have sharers, it is passing
1178 // When the packet metadata arrives, the tag lookup will be done while
1214 // if this is a write through packet, we don't try to
1274 // When the packet metadata arrives, the tag lookup will be done while
1280 // If this a write-through packet it will be sent to cache below
1389 // packet has sharers, thus the line is never allocated as Owned
1678 Packet packet(request, MemCmd::WriteReq);
1679 packet.dataStatic(blk.data);
1681 memSidePort.sendFunctional(&packet);
1728 // no allocation mode, and we have a write packet with an MSHR
1753 // MSHR request, proceed to get the packet to send downstream
1761 // make copy of current packet to forward, keep current
1773 // the packet so that the destination xbar can determine that
1774 // there will be a follow-up write packet as well.
1780 // delete the packet and will be creating a new packet
1787 // care about this packet and might override it before
1791 // As part of the call to sendTimingReq the packet is
1807 DPRINTF(CacheVerbose, "%s: packet %s found block: %s\n",
1835 // care about this packet and might override it before
2489 // Just forward the packet if caches are disabled.
2490 // @todo This should really enqueue the packet rather
2613 // snoop responses have their own packet queue and thus schedule