From e317d8b9ff611f16e116946054ac9a90cb453300 Mon Sep 17 00:00:00 2001 From: Andreas Hansson Date: Wed, 22 Aug 2012 11:39:56 -0400 Subject: Port: Extend the QueuedPort interface and use where appropriate This patch extends the queued port interfaces with methods for scheduling the transmission of a timing request/response. The methods are named similar to the corresponding sendTiming(Snoop)Req/Resp, replacing the "send" with "sched". As the queues are currently unbounded, the methods always succeed and hence do not return a value. This functionality was previously provided in the subclasses by calling PacketQueue::schedSendTiming with the appropriate parameters. With this change, there is no need to introduce these extra methods in the subclasses, and the use of the queued interface is more uniform and explicit. --- src/mem/tport.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/mem/tport.cc') diff --git a/src/mem/tport.cc b/src/mem/tport.cc index b5f775a56..7a0dd7cd9 100644 --- a/src/mem/tport.cc +++ b/src/mem/tport.cc @@ -82,7 +82,7 @@ SimpleTimingPort::recvTimingReq(PacketPtr pkt) // recvAtomic() should already have turned packet into // atomic response assert(pkt->isResponse()); - queue.schedSendTiming(pkt, curTick() + latency); + schedTimingResp(pkt, curTick() + latency); } else { /// @todo nominally we should just delete the packet here. /// Until 4-phase stuff we can't because the sending -- cgit v1.2.3