summaryrefslogtreecommitdiff
path: root/src/mem/bridge.hh
diff options
context:
space:
mode:
authorAli Saidi <Ali.Saidi@ARM.com>2012-06-05 01:23:08 -0400
committerAli Saidi <Ali.Saidi@ARM.com>2012-06-05 01:23:08 -0400
commit1b370431d0ac51eb54bfbf17247f935d48995a34 (patch)
treee9b90a8f9bdf914f29a20b3c287dae5b5a16db4c /src/mem/bridge.hh
parentd6997777bee827c89578cf730b186991485c647c (diff)
downloadgem5-1b370431d0ac51eb54bfbf17247f935d48995a34.tar.xz
sim: Remove FastAlloc
While FastAlloc provides a small performance increase (~1.5%) over regular malloc it isn't thread safe. After removing FastAlloc and using tcmalloc I've seen a performance increase of 12% over libc malloc when running twolf for ARM.
Diffstat (limited to 'src/mem/bridge.hh')
-rw-r--r--src/mem/bridge.hh3
1 files changed, 1 insertions, 2 deletions
diff --git a/src/mem/bridge.hh b/src/mem/bridge.hh
index 7342f4a9f..4595cf516 100644
--- a/src/mem/bridge.hh
+++ b/src/mem/bridge.hh
@@ -55,7 +55,6 @@
#include <queue>
#include <string>
-#include "base/fast_alloc.hh"
#include "base/types.hh"
#include "mem/mem_object.hh"
#include "mem/packet.hh"
@@ -85,7 +84,7 @@ class Bridge : public MemObject
* state and original source. It has enough information to also
* restore the response once it comes back to the bridge.
*/
- class RequestState : public Packet::SenderState, public FastAlloc
+ class RequestState : public Packet::SenderState
{
public: